Friday, July 19, 2013
Sunday, July 14, 2013
Fun with QR Codes
In honor of xkcd's cartoon today, I thought I'd make myself a qr code--a self portrait.
Be sure to follow the QR code in xkcd a couple times and then come back and try this self-portrait. Oh, and you can do your own QR code art at http://www.qrpixel.com/
Be sure to follow the QR code in xkcd a couple times and then come back and try this self-portrait. Oh, and you can do your own QR code art at http://www.qrpixel.com/
Tuesday, July 9, 2013
OpenStack Programs Core Developers
It seems to be something I look up fairly regularly: A listing of OpenStack core developers--either so I can get a +2 or just because I need to know if someone is on or not-on a given list.
I found the Canonical list by initially proposing in this blog the wrong list--and apparently that's a fairly common problem. So I'll link to the real list and explain how you might also be referring to the wrong list as well.
Official OpenStack Programs
OpenStack Technical Committee
Now for the wrong list. Not so long ago, much of OpenStack was managed in Launchpad. Consequently, there are also a somewhat correlating list of -core projects in Launchpad. However, I'm not going to reproduce them herein in order to avoid perpetuating them. I will mention the bug that has been posted to help clean them up though: https://bugs.launchpad.net/openstack-ci/+bug/1160277 and it is listed as in progress and did see some activity last month. If you happen to stumble onto this blog post and have some ownership over those dangling -core teams or other defunct/obsolete launchpad teams, go ahead and clean them up (pretty please).
Oh and one other editorial footnote: OpenStack now refers to the individual areas of development as programs, not projects as it used to. You might want to update your mental model to that terminology. Many thanks to ttx for the review of this document (though all errors and faux pas are mine.)
I found the Canonical list by initially proposing in this blog the wrong list--and apparently that's a fairly common problem. So I'll link to the real list and explain how you might also be referring to the wrong list as well.
Official OpenStack Programs
OpenStack Technical Committee
- Nova core
- Glance core
- Swift core
- Horizon core
- Keystone core
- Cinder core
- Neutron core
- Ceilometer core
- Heat core
- OpenStack Doc core
Now for the wrong list. Not so long ago, much of OpenStack was managed in Launchpad. Consequently, there are also a somewhat correlating list of -core projects in Launchpad. However, I'm not going to reproduce them herein in order to avoid perpetuating them. I will mention the bug that has been posted to help clean them up though: https://bugs.launchpad.net/openstack-ci/+bug/1160277 and it is listed as in progress and did see some activity last month. If you happen to stumble onto this blog post and have some ownership over those dangling -core teams or other defunct/obsolete launchpad teams, go ahead and clean them up (pretty please).
Oh and one other editorial footnote: OpenStack now refers to the individual areas of development as programs, not projects as it used to. You might want to update your mental model to that terminology. Many thanks to ttx for the review of this document (though all errors and faux pas are mine.)
Friday, July 5, 2013
VirtualBox Host-Only Networking
VirtualBox allows one to configure a VM with host-only networking. This can be useful if you are connnecting a number of VMs together and need to put them on the same switch/bridge.
However, it's darn frustrating to figure out how to enable it as all of the googling and manuals indicate you just enable it by selecting settings within the VM.
What they fail to mention though (but is covered in the built-in help in VirtualBox), is that you must first create a device for this host-only networking to use. From the main VirtualBox window, choose Preferences (below the File) menu. That will bring up the global preferences for the VirtualBox hypervisor. Click "Network" and then the "+" sign to add a host-only network device (typically vboxnet0).
It's possible that some versions of VirtualBox create one of these at install time, but on Ubuntu, such is not the case. Now you can create a number of virtual machines and put them on the same nic. Your host OS will also now show that same nic. Here's an example from my laptop's OS:
medberry@handsofblue:~$ ip a show dev vboxnet0
6: vboxnet0: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.56.1/24 brd 192.168.56.255 scope global vboxnet0
inet6 fe80::800:27ff:fe00:0/64 scope link
valid_lft forever preferred_lft forever
medberry@handsofblue:~$
However, it's darn frustrating to figure out how to enable it as all of the googling and manuals indicate you just enable it by selecting settings within the VM.
What they fail to mention though (but is covered in the built-in help in VirtualBox), is that you must first create a device for this host-only networking to use. From the main VirtualBox window, choose Preferences (below the File) menu. That will bring up the global preferences for the VirtualBox hypervisor. Click "Network" and then the "+" sign to add a host-only network device (typically vboxnet0).
It's possible that some versions of VirtualBox create one of these at install time, but on Ubuntu, such is not the case. Now you can create a number of virtual machines and put them on the same nic. Your host OS will also now show that same nic. Here's an example from my laptop's OS:
medberry@handsofblue:~$ ip a show dev vboxnet0
6: vboxnet0:
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.56.1/24 brd 192.168.56.255 scope global vboxnet0
inet6 fe80::800:27ff:fe00:0/64 scope link
valid_lft forever preferred_lft forever
medberry@handsofblue:~$
and that same vboxnet0 is now an option when you select host-only networking in the vm:
Subscribe to:
Posts (Atom)
