Hi Daniel,
Did you solve your problem? If yes, what was the solution? I am
interested because I have similar issues in my setup.
BR
Johanna
From: openstack-bounces+johanna.heinonen=nsn@lists.launchpad.net
[mailto:openstack-bounces+johanna.heinonen=nsn@lists.launchpad.net]
On
John,
Could you please share a link to the materials of the discussion you've
mentioned, or may be place where the discussion takes place (if it's
online)? We're currently working on RD project that involves prototype
implementation of regions, and I'm eager to see suggestions for replication
Folks,
I'd like to add to this that physical server metering shouldn't be treated
differently in Ceilometer now that bare metal provisioning framework enters
into Grizzly. Physical servers will just become billable resources much like
VMs. I am not speaking of physical server monitoring here.
Not sure if it helps bumping my own email, but here's a launchpad question
as well. Still haven't been able to solve this, it's keeping us from
transitioning our windows tests from eucalyptus.
https://answers.launchpad.net/nova/+question/212734
--Erik
On Mon, Oct 29, 2012 at 1:20 PM, Erik
If you are using Ubuntu, you can just
# sudo apt-get install cloud-init
there some wiki about heat, and how to install cloud-init.
https://github.com/heat-api/heat/wiki
best regards,
gtt
? 2012?10?31? 02:30, AK Sathiya ??:
All, I would like to install the cloud init on the custom image that i
All the instances are stuck in task scheduling, some suggestion:
Is nova-scheduler running?
Is rabbitmq running?
Is rabbitmq_host right in nova.conf?
? 2012?10?31? 17:01, Desta Haileselassie Hagos ??:
netease mail Hi All,
VM instances are stuck in build state for three days as you can see it
Hi Johanna,
are you running Openstack with Quantum or nova-network? In the former case,
which plugin are you using?
If you are using nova-network, which network manager are you using?
Salvatore
On 2 November 2012 06:32, Heinonen, Johanna (NSN - FI/Espoo)
johanna.heino...@nsn.com wrote:
Hi
Hi sir,
I am very glad to write the Email to you,My name is jiangping who is an
engineer majors in openstack from jovaunn.com,hangzhou,China!!!I have
established the environment of openstack successfully by inputing
tools/with_venv.sh ./manage.py runserver 0.0.0.0:8080 in terminal and
Hi jiangping,
How many compute nodes you have? if just one, you should add
'allow_resize_to_same_host=True' to /etc/nova/nova.conf, and retry.
if you have more than one compute nodes, it more troublesome, you should be
able to ssh to each other between compute nodes WITHOUT inputting password.
Greetings Skible.
Great work to you and the rest on the guide. A minor change is required in
nova.conf configuration for file VNC. The parameter for
vncserver_proxyclient_address must be eth0's IP address, otherwise the console
reports 'failed to connect to server'.
Good morning,
Perhaps I have not explained properly…. I have different IBM arrays whose disks
are disks of different speeds… and wanted to have the possibility of
provisioning vm on different speed storages for example…. Could this be
possible??… I'm using XCP (1.5, 1.1 and 1.6 versions so I
Hi all,
I am running openstack, with XCP on ubuntu 12.04.
When I tried to launch instance using the majority of existing flavors, I
noticed that the instance never takes into account the mentioned disk space.
I also tried to create a new flavor with Ephemeral disk, but this does not
solve the
Or unless… If I had to use forcibly the same storage…. for all vm provisioned
in a single nova-compute…. is it anyway of saying Openstack to create a vm in a
nova-compute or another one… depending on the storage attached to the
nova-compute's dom0??
El 02/11/2012, a las 10:25, Egoitz
Hi Ian,
Many thanks for the remark. i fixed it :)
Le 02/11/2012 10:22, DarkSinclair a écrit :
Greetings Skible.
Great work to you and the rest on the guide. A minor change is required in
nova.conf configuration for file VNC. The parameter for
vncserver_proxyclient_address must be eth0's
Hello Stackers,
i am reading this
http://docs.openstack.org/developer/horizon/releases/2012_2.html when i
got to the limitations part !
Does anyone have anyidea when the fixes will be submitted ? i really
need to provide my users with an easy way to associate floating IPs :)
Cheers !
yes , it's works, thanks all !
On Mon, Oct 22, 2012 at 6:17 PM, Pádraig Brady p...@draigbrady.com wrote:
On 10/22/2012 10:33 AM, hzguanqiang wrote:
Hi Pádraig
I think you are right. I met the same probelm just as 念远 did when I tried
lxc with openstack folsom.
To solve the problem, I tried
Hi ,
I have a setup, which includes
Folsom Controller (Ubunut 12.04)
Folsom Compute Node (Ubunut 12.04)
Folsom Compute Node (IBM Power PC)
I am able to create instances on IBM Power PC, but not able get ip address
from dnsmasq.
Instances created on X86 compute node are getting ip address from
Ok, I figured out my problem. My nova.conf BEFORE:
virt_mkfs=default=mkfs.ext4 -L %(fs_label)s -F %(target)s
virt_mkfs=windows=mkfs.ntfs --force --fast --label %(fs_label)s %(target)s
This is from the docs, but it's not right. Removing the citation marks made
it work as expected:
Are those not the default settings?
https://github.com/openstack/nova/blob/master/nova/virt/disk/api.py#L66
Thanks,
Kiall
On Fri, Nov 2, 2012 at 11:21 AM, Erik Lindblad erik.lindb...@gmail.comwrote:
Ok, I figured out my problem. My nova.conf BEFORE:
virt_mkfs=default=mkfs.ext4 -L
Hi,
I just want to get data from a custom table created in Quantum and show it
in horizon.(Just like list networks in horizon)
I followed same architecture followed for showing Networks in horizon.
I am able to send the request to quantum-server. And query also executing
fine and getting data as a
Hi Veera,
Is your setup using nova-network or Quantum?
what network services are you running in the controller node?
If you're using quantum you might provide information about the plugin
you're using; in case of nova-network, knowing which network manager you're
running might help the community
Hi all,
I am totally new to Folsom and just wanted to get into it.
I followed installation instructions from this guide :
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
Everything went fine till the end(Horizon) but when
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
Well, What I am trying to find is if an instance in nova is low in
resources, then another instance should be automatically created and
started.
Is this possible or any tools are out for this?
Paras.
On Fri, Oct 26, 2012 at 3:23 PM, Debo Dutta ddu...@gmail.com wrote:
That is a very good idea
Yong Sheng Gong also did some slides that provide a nice deep-dive on
Quantum internals: see the Slides on Technical Architecture of
Quantumhttp://wiki.openstack.org/Quantum?action=AttachFiledo=gettarget=quantum-technical-archicture
link on http://wiki.openstack.org/Quantum
dan
On Fri, Nov 2,
Hi guys
I'm struggling with VLAN Manager in Nova.
I want to have 3 VLANs, one for each project. These ranges have been
created in my network and the tagged ports are connected to my server.
I want to create VMs that just take an IP from these networks and get
bridged on to the network.
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.
Highlights of the week
Videos of OpenStack Summit Fall 2012 published
http://www.openstack.org/summit/san-diego-2012/openstack-summit-sessions/
The Summit was packed with amazing content, including user stories from
Cisco WebEx, Living Social and CERN, 100+ developer working
Hi,
If I understand your request correctly, say you have two storage backends
with different QoS and you want to use both of them in your OpenStack/XCP
deployment, what you can do is:
1) create SR1 for XCP1 that maps to storage array at QoS1
1a) configure the compute domU for XCP1 to point to
Good afternoon Armando,
Thanks a lot for you're answer.
Yes basically I want to setup a virtual housing service in the way you can
create a machine in sas or sata storage for example. If each nova-compute
should point to just one sr (storage kind) of xcp it would be one or the other
one (in
Well, I'm not really sure if the configuration parameters are
hierarchical. I haven't given much thought on the internal
organization of various parameters in all configuration files and
their inter-dependencies. However I feel that the parameters that
govern the behaviour of openstack components
On Thu, Nov 01, 2012 at 11:03:14AM -0700, Vishvananda Ishaya wrote:
The new config drive code defaults to iso-9660, so that should work. The
vfat version should probably create a partition table.
Is that what Folsom is using? Or is it new-er than that?
--
Lars Kellogg-Stedman
On 11/02/2012 07:03 PM, Lars Kellogg-Stedman wrote:
On Thu, Nov 01, 2012 at 11:03:14AM -0700, Vishvananda Ishaya wrote:
The new config drive code defaults to iso-9660, so that should work. The
vfat version should probably create a partition table.
Is that what Folsom is using? Or is it
Egoirz,
On Fri, Nov 2, 2012 at 6:29 PM, Egoitz Aurrekoetxea Aurre
ego...@ramattack.net wrote:
Good afternoon Armando,
Thanks a lot for you're answer.
Yes basically I want to setup a virtual housing service in the way you can
create a machine in sas or sata storage for example. If each
Egoirz Aurrekoetxea Aurre
ego...@ramattack.net
Sent from my smartphone
El 02/11/2012, a las 21:12, Armando Migliaccio amigliac...@internap.com
escribió:
Egoirz,
On Fri, Nov 2, 2012 at 6:29 PM, Egoitz Aurrekoetxea Aurre
ego...@ramattack.net wrote:
Good afternoon Armando,
Thanks a lot
Yes, I am assuming the service controller provides a different stream of
data from the lower level VM events. So the question is how to represent
and store this additional meta data in ceilometer. Note that there
doesn't necessarily need to be a linkage/grouping between the resources
since the
On 01/11/12 13:58 -0700, Jeffrey Budzinski wrote:
Thanks for putting that together Sandy. Very nice!
From my perspective, there are two major things that are undesirable for us:
1) Putting this data through the queue is not something that feels right. We'd like to
have to option to use other
On 02/11/12 10:47 -0500, Paras pradhan wrote:
Well, What I am trying to find is if an instance in nova is low in
resources, then another instance should be automatically created and
started.
Is this possible or any tools are out for this?
You can give the heat project a go.
I create a windows 7 image(without activate) and upload to glance, and I
can successfully start it up. But how can I automatically activate it after
user launch it? Or how can I inject the SN into windows during startup? Or
any other better idea?
Thanks a lot.
- Ray
Yours faithfully, Kind
On Sat, Nov 03, 2012 at 10:00:40AM +0800, Ray Sun wrote:
I create a windows 7 image(without activate) and upload to glance, and I
can successfully start it up. But how can I automatically activate it
after user launch it? Or how can I inject the SN into windows during
startup? Or
As we start to file QA blueprints, which of these is the right place to
do them in:
https://blueprints.launchpad.net/openstack-qa or
https://blueprints.launchpad.net/tempest or is there some 3rd place we
should use?
The first one seems more generically useful, but there's a lot of old
On 11/01/2012 03:45 PM, Sean Dague wrote:
As we start to file QA blueprints, which of these is the right place to
do them in:
https://blueprints.launchpad.net/openstack-qa or
No, this is the QA documentation.
https://blueprints.launchpad.net/tempest or is there some 3rd place we
should
On 11/01/2012 04:49 PM, David Kranz wrote:
There is now a full tempest run going daily and reporting failures to
this list. But that won't work because
jenkins and gerrit cannot be launchpad members. According to the ci
folks, others have dealt with this
by moving their mailing lists to
Not a problem at all. All I need is:
- name of the list (I assume it's: openstack...@lists.openstack.org)
- one terse line to describe the list on http://lists.openstack.org
- one or more paragraphs to describe the list on its page
- email address of the administrator(s)
Cheers,
stef
On Fri 02
On 11/02/2012 11:43 AM, Stefano Maffulli wrote:
Not a problem at all. All I need is:
- name of the list (I assume it's: openstack...@lists.openstack.org)
Yes.
- one terse line to describe the list on http://lists.openstack.org
All Things QA.
- one or more paragraphs to describe the
Out of the nova live upgrade, and full gate in tempest sessions at
OpenStack Summit I think I've come up with the following blueprints that
we should be looking at over grizzly.
* tempest-testtools - remove nose from tempest and use testtools/testr
instead (this conversation mostly happened
at 20121102-0204Build needed 00:01:36
at 20121102-0205Build needed 00:01:18
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/8/Project:precise_grizzly_nova_trunkDate of build:Fri, 02 Nov 2012 03:31:23 -0400Build duration:2 min 20 secBuild cause:Started by an SCM changeBuilt
at 20121102-0346Build needed 00:10:01, 95788k disc spaceERROR:root:Error occurred
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/9/Project:precise_grizzly_nova_trunkDate of build:Fri, 02 Nov 2012 04:31:23 -0400Build duration:2 min 17 secBuild cause:Started by an SCM changeBuilt
at 20121102-0446Build needed 00:10:00, 95788k disc
at 20121102-0722Build needed 00:01:46, 10804k disc spaceERROR:root:Error occurred during package creation/build: Command
Title: raring_grizzly_keystone_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/5/Project:raring_grizzly_keystone_trunkDate of build:Fri, 02 Nov 2012 08:00:11 -0400Build duration:5 min 54 secBuild cause:Started by user Adam
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/10/Project:precise_grizzly_nova_trunkDate of build:Fri, 02 Nov 2012 09:01:23 -0400Build duration:2 min 24 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/11/Project:precise_grizzly_nova_trunkDate of build:Fri, 02 Nov 2012 12:01:24 -0400Build duration:3 min 1 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_python-quantumclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-quantumclient_trunk/2/Project:precise_grizzly_python-quantumclient_trunkDate of build:Fri, 02 Nov 2012 12:31:21 -0400Build duration:3 min 19 secBuild
at 20121102
Title: precise_grizzly_python-cinderclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-cinderclient_trunk/4/Project:precise_grizzly_python-cinderclient_trunkDate of build:Fri, 02 Nov 2012 16:31:21 -0400Build duration:3 min 38 secBuild
at 20121102
at 20121102
Title: precise_grizzly_swift_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_swift_trunk/7/Project:precise_grizzly_swift_trunkDate of build:Sat, 03 Nov 2012 01:31:21 -0400Build duration:3 min 4 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_swift_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_swift_trunk/7/Project:raring_grizzly_swift_trunkDate of build:Sat, 03 Nov 2012 01:31:21 -0400Build duration:3 min 29 secBuild cause:Started by an SCM changeBuilt
63 matches
Mail list logo
