Hello all,
I am running Folsom with Quantum v2, via Devstack. Am trying to use Ubuntu UEC
image to spawn VMs, but when the VM instance boots, it is not able to contact
the metadata server in order to (among other things) inject the public key
needed in order for me to be able to SSH into the in
.org/trunk/openstack-network/admin/content/ch_limit
ations.html). For Grizzly, we have added metadata service for
overlapping networks. This feature is currently available in devstack
when you enable the q-meta service.
mark
On Jan 2, 2013, at 11:10 PM, Willard Dennis
wrote:
> Hello all,
&
See
http://www.microsoft.com/licensing/existing-customers/product-activation-faq.aspx
Looks like KMS would be the appropriate means; your MSFT reseller would sell
you a KMS license key to use for the appropriate pool of server / app
instances, then it is loaded into the KMS server, which the
Hi Lei,
Perhaps this article I wrote on the packetpushers.net blog can be helpful to
you --
http://packetpushers.net/openstack-quantum-network-implementation-in-linux/
Best,
Will
From: Lei Zhang
Sent: February 6, 2013 1:40 AM
To: openstack@lists.launchpad.net
Subject: Re:
Hi all,
We’ve been playing around with a single-server install of (Folsom) Devstack,
and have now decided to do the deal and create a multi-node OpenStack
installation. The installation is going to be for research use for a single
tenant (the owning research dept) and should not grow that mu
Thanks, guys, for your responses. I will check out the respective guides you’ve
mentioned, and hopefully we can make Quantum work for our simple use case.
Best,
Will
On Mar 22, 2013 4:32 PM, "Willard Dennis" wrote:
Hi all,
We’ve been playing around with a single-server
6 matches
Mail list logo
