Re: [Openstack] Boot from Volume via Horizon?
Ah! Touche! What a nicer option to start instances based on volumes :-) I was hoping also for a button or option from the Volumes or Snapshots areas of the web app as well, but this works (albeit being a bit hidden). -- Wolf On Wed, Jun 12, 2013 at 5:13 AM, Julie Pichon jpic...@redhat.com wrote: Hi, Wolfgang Richter w...@cs.cmu.edu wrote: Am I missing something or does Horizon as released with Grizzly not have an option for booting an instance from a volume? When you click on the button to Launch an instance on the Instances page, you should see a Volume Options tab that will let you choose a volume or volume snapshot to boot from. Hope this helps, Julie I am able to successfully do this with nova boot from the commandline. -- Wolf ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Wolf ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Boot from Volume via Horizon?
Am I missing something or does Horizon as released with Grizzly not have an option for booting an instance from a volume? I am able to successfully do this with nova boot from the commandline. -- Wolf ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Cinder Callbacks from nova-compute
My nova-compute nodes appear to be using a hostname for my Cinder host that is incorrect. How do I set the hostname for the cinder-volume host on each nova-compute node? Some setting in /etc/nova/nova.conf? -- Wolf ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Cinder Callbacks from nova-compute
Fixed the issue.
Turns out Keystone was providing a URL (from the database driver) that I
didn't want it to use for callbacks (nova-compute on a compute server):
I manually updated the table 'endpoint' in the 'keystone' database to
change the URL for the 'public' interface associated with 'cinder' (URL
using port 8776) to point to an internal IP.
Is this desired behavior? nova-compute is contacting the 'public'
interface of a service ('cinder')? Why aren't the OpenStack components
using the 'internal' URL? What is the distinction here?
--
Wolf
On Fri, Jun 7, 2013 at 12:42 PM, Wolfgang Richter w...@cs.cmu.edu wrote:
My nova-compute nodes appear to be using a hostname for my Cinder host
that is incorrect.
How do I set the hostname for the cinder-volume host on each nova-compute
node?
Some setting in /etc/nova/nova.conf?
--
Wolf
--
Wolf
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] About over-commit memory
The third VM is of the same flavor as the other two? At least, it is only trying to use 2GB RAM as well? Which hypervisor is in use (kvm)? -- Wolf On Thu, Jun 21, 2012 at 6:03 PM, Sam Su susltd...@gmail.com wrote: Hi Vish, Thank you for your response. I added a 'line ram_allocation_ratio=10' in nova.conf, then restarted nova-scheduler in control node. after that was done, I tried to create a VM, but it still failed, and the debug info is showing as below: http://pastebin.com/RDHb9fDU Can you help me to take a look at the error info at your convenience? Thanks, Sam On Thu, Jun 21, 2012 at 12:23 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: Try setting: ram_allocation_ratio=10 in your nova.conf (it defaults to 1.5) Vish On Jun 21, 2012, at 11:34 AM, Sam Su wrote: Hi, I have a mini openstack environment with one compute node and one nova control node. There is 4G memory in the compute node, and I have allocated 2 VMs with 2G memory for each VM. When I try to create another VM , I get the error as below: http://pastebin.com/QZMQvXtB I am wondering whether Openstack has support memory overcommit? How to do this? It will be much appreciated If someone can give me some hints about this in convenience. Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] About over-commit memory
What is the intention of overcommit here? Is it allowable (possible?) to have a single VM with more RAM allocated than any physical machine? Or VMs allocated/running that together are more than available RAM? -- Wolf On Jun 21, 2012, at 6:13 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: I just noticed there is a bug in ram_allocation_ratio, it actually only multiplies the check for free ram which doen't do a lot. Bug filed here: https://bugs.launchpad.net/nova/+bug/1016273 In the meantime, to overcommit you will have to disable the ram check completely by setting the following set of enabled filters in conf. scheduler_default_filters=AvailabilityZoneFilter,ComputeFilter Vish On Jun 21, 2012, at 3:03 PM, Sam Su wrote: Hi Vish, Thank you for your response. I added a 'line ram_allocation_ratio=10' in nova.conf, then restarted nova-scheduler in control node. after that was done, I tried to create a VM, but it still failed, and the debug info is showing as below: http://pastebin.com/RDHb9fDU Can you help me to take a look at the error info at your convenience? Thanks, Sam On Thu, Jun 21, 2012 at 12:23 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: Try setting: ram_allocation_ratio=10 in your nova.conf (it defaults to 1.5) Vish On Jun 21, 2012, at 11:34 AM, Sam Su wrote: Hi, I have a mini openstack environment with one compute node and one nova control node. There is 4G memory in the compute node, and I have allocated 2 VMs with 2G memory for each VM. When I try to create another VM , I get the error as below: http://pastebin.com/QZMQvXtB I am wondering whether Openstack has support memory overcommit? How to do this? It will be much appreciated If someone can give me some hints about this in convenience. Thanks, Sam ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
