Agile Notes

Bubblebridge is in place but since its a full fledged CentOs 6.3 desktop distro why not have proper access to it. So I thought I would enable VNC on it. Installation Just to make sure check that vnc or rather tigervnc is installed executing the following: rpm -q tigervnc-server rpm -q tigervnc If not present the following should cure that : yum install tigervnc-server tigervnc Setup VNC user accounts. Unless you want to run as an already existing user the following would create a user (or if repeated) users for you. As root. useradd passwd In my case I'll go with the bubblebridge user the above is already fixed. Next step is to edit the server configuration file  /etc/sysconfig/vncservers adding the following at the end. VNCSERVERS="2: " VNCSERVERARGS[2]="-geometry 800x600" Now its time to setup the vncpasswd for the users by su:ing out of root to the users. su - vncpasswd exit Check that the server starts and...

Networking Revised After adding a few more NICs to bubblebridge for the production Vlan's I realize that this starts to become ridiculous. 50 Vlans means 51 NIC's in bubblebridge... There has to be a better way! So in my case I believe that this alternative setup for bubblebridge is more maintainable. In this scenario I create a vlan trunk for all vlans in the recovery setup. This means that there only has to be one NIC attached to the vlan trunk in the bubblebridge server. Unfortunately its still a ton of configuration to do. This is the alternative setup and the steps to reach it. As root - fix the 70-persistent-net.rules file. # This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key. # PCI device 0x15ad:0x07b0 (vmxnet3) SUBSYSTEM=="net"...