Ask Your Question

Kiloseven's profile - activity

2015-05-04 03:55:50 -0600 received badge  Nice Answer (source)
2014-11-27 03:37:29 -0600 received badge  Famous Question (source)
2014-11-27 03:37:29 -0600 received badge  Notable Question (source)
2014-05-17 04:07:31 -0600 received badge  Famous Question (source)
2013-11-22 18:55:45 -0600 received badge  Autobiographer
2013-11-18 03:20:41 -0600 received badge  Famous Question (source)
2013-10-24 16:46:46 -0600 received badge  Popular Question (source)
2013-10-23 21:21:43 -0600 received badge  Teacher (source)
2013-10-22 12:40:47 -0600 commented question How to deal with a sudden power-off?

Not to sound snarky, but as with all other servers, battery backup?

2013-10-21 16:27:33 -0600 answered a question I wanted to install nova-compute, glance & keystone on 3 different machine... Could any one tell me what configuration changes i have to do???
2013-10-21 16:23:03 -0600 answered a question Are there published standards for OpenStack application compatibility?

Full compliance with the APIs for REST and compatability with Amazon's EC2 and S3 APIs. IBM has more detail here and here with coding standards documents also available.

2013-10-21 15:02:11 -0600 answered a question glance add problem

Suggest you try instead:

glance image-create --name Windows7 --is-public true --container-format bare --disk-format vmdk < /home/desktop/Windows7.vmdk

then advise the result of glance image-list

2013-10-21 14:59:48 -0600 commented question glance add problem

What does glance image-list show you?

2013-10-18 16:52:07 -0600 commented answer Why won't Nova start?

There's no in the system, checked with locate and find both. The output of nova service-list is a heading with nothing running. /usr/bin/nova-compute --config-file /etc/nova/nova.conf complains about nova-conductor not running, so I launched that then nova-compute, but the nova service-list is still empty. The Bilel procedure is at and I am in section 6, Nova.

2013-10-18 16:29:46 -0600 received badge  Notable Question (source)
2013-10-18 15:56:24 -0600 asked a question ┬┐Unable to restart libvert service?

I'm in the last step of section 6.1 for Nova and lvm in - but am unable to restart the libvert service despite following his procedure. I get

stop: Unknown job: libvirt-bin
start: unknown job: libvirt-bin

How may I find where this is failing, please?

2013-10-16 16:44:41 -0600 commented question What nova services can I restart without affecting my vm?

What does the *creds* file for that designated host look like?

2013-10-16 15:47:00 -0600 received badge  Commentator
2013-10-16 15:40:25 -0600 commented question Why won't Nova start? explains the preferred method, better than installing and using sysv-rc-conf which is soooo RedHat...

2013-10-16 13:23:31 -0600 commented question Why won't Nova start?

Ain't no chkconfig in Ubuntu. Using Ubuntu 13.04 server as base for server as per the aforementioned instructions cited above. suggested use of sysv-rc-conf which I shall go explore. Thank you kindly for the tip, too!

2013-10-16 01:04:48 -0600 received badge  Popular Question (source)
2013-10-15 14:39:22 -0600 asked a question Why won't Nova start?

Still mushing my way through Bilel Msekni's OpenStack Grizzly Install Guide for a single-server install.

Nova has stopped. It worked before, but now /var/log/boot.log shows the Nova services (only) fail at boot time.

I have a Keystone user-list and a Glance image-list, so my creds file is OK, but as per the Nova section of the instructions first cited above, when I run nova-manage service list I should see an instance of Nova running, and I do not, just the title line but no data.

FYI, eth0 as per ifconfig is on and eth1, set as the primary web interface when Ubuntu 13.04 was installed, is dhcp'd so I can reach the web. /etc/network/interfaces has these active lines as per this step in the procedure:

auto lo
iface lo inet loopback
auto eth1
iface eth1 inet dhcp
auto eth0
iface eth0 inet static

Your kind help would truly be appreciated.

2013-10-15 12:58:57 -0600 commented answer Can't reach metadata server from VM running in single instance setup

Doesn't an APIPA address suggest a NIC / HA which isn't getting either DHCP or a manually defined IP address, and therefore it parks itself over in 169.254 where it's out of the way and won't interfere with IP traffic?

2013-10-15 12:09:54 -0600 answered a question Where can I find details about vlan and gre network types?

GRE tunneling with the openvswitch plugin requires OVS kernel modules that are not part of the Linux kernel source tree. These modules are not available in certain Linux distributions, including Fedora and RHEL. Tunneling must not be configured on systems without the needed kernel modules. The Open vSwitch web site indicates the OVS GRE tunnel support is being moved into the kernel source tree, but patch ports are not. Once GRE support is available, it should be possible to support tunneling by using veth devices instead of patch ports.

Nova and Quantum currently assume all nodes where VMs are run will have access to all virtual networks. Cases where not all nodes have connections to all physical networks used with Quantum would be much better supported, if the Nova scheduler could query Quantum to determine whether a particular compute node supports the needed virtual networks.

Therefore, vlan is the preferred approach, if your configuration will support it. Otherwise, you might find yourself without all the troubleshooting tools available should something fail (and it always does).

2013-10-15 11:56:48 -0600 received badge  Notable Question (source)
2013-10-14 20:51:56 -0600 answered a question How to find the credentials to be used ?

Well, create new a new creds file (preferably in a directory beneath your home where you keep all other scripts and miscellany OpenStack-related) and then do source /path/credsfile, substituting the path and creds file to match the name you used.

2013-10-14 19:08:40 -0600 received badge  Popular Question (source)
2013-10-14 16:36:47 -0600 marked best answer What is my path to Cinder? tells me "Note: Beware that this volume group gets lost after a system reboot. (Click Here to know how to load it after a reboot)"

So I follow Here to which tells me to edit /etc/rc.local to add losetup /dev/loop2 %Your_path_to_cinder_volumes%

Since I am setting up a single-server system using LVM as per his instructions, I tried cinder-volumes (fails with No such file or directory as well as /var/lib/cinder * and */var/lib/cinder/volumes (fails with /var/whatever is a directory).

When following his instructions (and I have searched, thrice, for path within them to try to find something else), prithee kind geniuses, where is this path of which he speaks?

2013-10-14 16:05:53 -0600 answered a question now i am working small scale IT company.i am go to implement openstack in our kindly give some idea about the hardware minimum requirements.Thank You and gives some insight. I would also make sure your single-server is also kvm-capable with

apt-get install cpu-checker

as well as meeting the requirements stated above.

And, as the workload increases, you will need more servers to spread out the system (adding Compute Nodes and Network Nodes), more hard drive space for the database and more RAM for all. At that point, the answer degenerates into a 'How High Is Up?' discussion, because I don't know what you want to do with it. Is this just for development/experimentation, or do you want to do something with it?

You might also just consider a very simple RDO setup on CentOS, Scientific Linux or, of course, RHEL.

Your mileage may vary, of course. I have seen smaller, but the folks doing it upgrade really rapidly.

And, are you near an OpenStack UserGroup? See for a worldwide map.

2013-10-14 15:49:23 -0600 commented question Why do I get errors when I run

No difference. 1st install it didn't, now it does, still fails
The open vswitch pt 2 setup says to edit /etc/network/interfaces to be like this:

# VM internet Access
auto eth2
iface eth2 inet manual
up ifconfig $IFACE up
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off
down ifconfig $IFACE down

Big fail. Since I don't use eth2, + eth1 is for my LAN connection, changed to eth0 (which is idle) to adapt steps 4.2 + 2.2 to my setup, + commented the last 4 lines which also caused Big Fail:

auto eth0
iface eth0 inet manual
# up ifconfig $IFACE up
# up ip link set $IFACE promisc on
# do ip link set $IFACE promisc ... (more)