Hi Stackers,
We have a small Openstack lab using three servers. The components are
distributed as:
1. Network controller - Quantum L3 DHCP, L2 agent, Nova, Openvswitch
2. Cloud controller - Quantum server, L2 agent, Nova, Openvswitch,
Dashboard, API, MySQL, Rabbitmq
3. Compute node - Nova,
On Wed, Nov 7, 2012 at 5:52 PM, Gary Kotton gkot...@redhat.com wrote:
On 11/07/2012 11:47 AM, Aniruddha Khadkikar wrote:
Hi Stackers,
We have a small Openstack lab using three servers. The components are
distributed as:
1. Network controller - Quantum L3 DHCP, L2 agent, Nova, Openvswitch
On Nov 4, 2012 8:16 PM, Nah, Zhongyue zhongyue@intel.com wrote:
https://blueprints.launchpad.net/nova/+spec/deployer-friendly-confs
This blueprint seems to be planning to implement what is being discussed
for Nova.
Marvellous. I believe this discussion adds/reinforces to the ideas
On Sun, Nov 4, 2012 at 5:45 AM, Ray Sun qsun01...@cienet.com.cn wrote:
Is there any method to get the resource pool capability(CPU/Memory/Storage)
in the cloud? Can OpenStack auto detect the resource when a new node join
in?
If not, is there a roadmap to implement it?
My thoughts exactly.
of truth), or
you need a system (such as Puppet) that can parameterise what it
delivers based on e.g. the software version in question.
-Rob
On Sat, Nov 3, 2012 at 8:17 AM, Jonathan Proulx j...@csail.mit.edu wrote:
On Sat, Nov 03, 2012 at 12:19:58AM +0530, Aniruddha Khadkikar wrote:
: However I
On Sat, Nov 3, 2012 at 7:53 PM, andi abes andi.a...@gmail.com wrote:
On Sat, Nov 3, 2012 at 9:30 AM, Aniruddha Khadkikar
askhadki...@gmail.com wrote:
@Rob - excellent points. It would be good to know in real life
deployments how often are configurations changed so the question of
network
On Sat, Nov 3, 2012 at 9:06 PM, Tim Bell tim.b...@cern.ch wrote:
Puppet is great for this sort of thing. There are various ways of querying
parameters and making choices about them. A typical example would be where
you want to adjust a configuration parameter due to memory configuration or
Hi Stackers,
Are there plans to keep all configuration parameters in a central
location? Rather than having a lot of configuration files. By central
location I do not mean that its a single server but it could be a
distributed database with each node irrespective of purpose having a
copy of the
Are there plans to keep all configuration parameters in a central
location? Rather than having a lot of configuration files. By central
location I do not mean that its a single server but it could be a
distributed database with each node irrespective of purpose having a
copy of the configurations.
should be in a data store
that can be queried from a single data store. Also it would make
deployments less error prone.
Aniruddha
On Fri, Nov 2, 2012 at 11:52 PM, Endre Karlson endre.karl...@gmail.com wrote:
Are you thinking of something like a Hiera style thing?
Endre.
2012/11/2 Aniruddha
] On Behalf
Of Aniruddha Khadkikar
Sent: Wednesday, March 14, 2012 9:03 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] User experience and simplified configurations
Hi,
Its only recently that I have started exploring openstack and the first
thing that comes to my mind
11 matches
Mail list logo
