Hi Mike,
See Rhys post on that: http://www.rdoxenham.com/?p=275
HTH
On Sat, Jun 14, 2014 at 6:01 PM, Mike Spreitzer wrote:
> Suppose I have an OpenStack undercloud, deployed on some Intel Xeon
> E5-2670 boxes running Ubuntu 12.04. In /proc/cpuinfo I see the following
> flags: fpu vme de pse
Those VMs should be able to boot with on a Linux installation with a KVM
hypervisor with no issues, provided that you have the images (or can grab
them from Glance) and can create a .xml definition file for each.
For the xml definitions, you can cheat a little by creating a blank new KVM
VM using t
However, if removing the '--device' line boots the machine successfully,
you might want to simply check if your init ramfs (of the guest) has a
virtio block driver module included (doesn't seems so), include it (might
as well include the virtio network module) and rebuild it on your SuSE
image.
Se
If
> not, is there any way we can setup OpenStack (NOVA?) to setup the
> public-hostname metadata to the resolved public-ipv4 name automatically for
> each VM?
>
> Thanks,
>
> Gerard Bernabeu
> FermiCloud and FermiGrid Services at Fermilab
> Phone (+1) 630-840-6509
>
&g
Hi,
What are you trying to do? Do you need to attach/detach a cdrom often? If
it is to install the OS, you should either try a vendor shipped image or
create a custom one, save it and push it to your OpenStack deployment.
See here:
http://docs.openstack.org/trunk/openstack-compute/admin/conte
Understood, in this case, I would recommend you use Ubuntu 12.04 LTS images
for your testing.
Hope this helps.
On Mon, Sep 16, 2013 at 2:07 AM, sam lee wrote:
> @laclasse, @Ritesh, thanks for the help. I will try right now.
>
> @laclasse, I am quite a newbe for openstack, and ubuntu
Agreed, unique FQDNs on every instances is still a big issue for common
workloads, hopefully solved by DNS services coming to OpenStack soon... I
fully agree that the instance name and the FQDN of the instances should be
2 separate things, and even better, I think instances by default should try
a
There is some overlap, maybe due to certain public cloud services that have
decided to expose the glance API through nova, rather than exposing the
glance api end point directly. Not entirely sure of your end goal, but if
this is a private/custom install of OpenStack and you have the glance
servic
@sam lee, if I understand properly
you are talking about a custom Ubuntu image you created? IIRC all Ubuntu
provided default images for OpenStack/AWS after 10.04 LTS have this package
installed (or was it starting at 12.04 LTS? Scott Moser the maintainer of
the packahe might know more).
Also,
Install python-suds on the nodes to speak to the vsphere API.
See http://docs.openstack.org/trunk/openstack-compute/admin/content/vmware.html
Hope this helps.
On Wed, Sep 4, 2013 at 3:03 AM, openstack learner
wrote:
> Hi all,
>
> I am new to openstack, can anyone tell me if the openstack nova
Can you only change flavors of an instance or
> can you granularly adjust an intense? If I cant,that means I have to make a
> flavor for every little custom difference to an existing flavor?
>
>
> On 2013-08-30 02:18, laclasse wrote:
>>
>> That is correct, it does.
>
That is correct, it does.
Takes care of extending the rootfs of the instance according to the
flavours (sizes of VM) that you are defining/modifying or using the
pre-defined ones. See
http://docs.openstack.org/trunk/openstack-ops/content/flavors.html
On Fri, Aug 30, 2013 at 7:15 AM, Mark Chaney w
There is a good chance that your centos 5.6 image was not made on
virtIO block device for the root disk, hence the error trying to boot
on one.
Include a virtIO block driver in your base init ramdisk and rebuild it
(the ramdisk of the VM). Then it should work.
See:
https://bugzilla.redhat.com/show
13 matches
Mail list logo
