Hi!
I have implemented API for network creation a month ago
(https://review.openstack.org/#/c/9847/). The patch is still waiting
for approval.
Could somebody pay attention to it since it's a blocker for our
company, Grid Dynamics?
--
Alessio Ababilov
Software Engineer
Grid Dynamics
You can see what XenAPI exposes here:
http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/api/?c=VBD
I think the only thing you can influence when plugging in the disk is the
“userdevice” which is the disk position: 0,1,2…
When you have attached the disk you can find out the “device” name,
On Wed, Aug 15, 2012 at 03:49:45PM +0100, John Garbutt wrote:
You can see what XenAPI exposes here:
http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/api/?c=VBD
I think the only thing you can influence when plugging in the disk is the
“userdevice”
which is the disk position: 0,1,2…
Can you elaborate what is the purpose of this database?
If we compare it to KVM support, the 'primary' location of VMs' metadata
is in libvirt internal store (outside of Nova), and then it is cached in
Nova DB, for Nova purposes.
A similar approach might make for bare-metal machines too -- keep
From: Daniel P. Berrange [mailto:berra...@redhat.com]
On Wed, Aug 15, 2012 at 03:49:45PM +0100, John Garbutt wrote:
You can see what XenAPI exposes here:
http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/api/?c=VBD
I think the only thing you can influence when plugging in the disk is
Hi All,
Please review: https://review.openstack.org/#/c/11016/ - HTTP POST Notifier for
OpenStack projects.
Thanks Regards,
Unmesh Gurjar | Lead Engineer | NTT DATA Global Technology Services Private
Limited | w. +91.20.6604.1500 x 379 | m. +91.982.324.7631 |
unmesh.gur...@nttdata.com |
The bare-metal database includes five tables:
1. bm_nodes // This is similar to compute_node table
2. bm_deployments // The status of deployment of bare-metal nodes
3. bm_pxe_ips // PXE information for bare-metal nodes
4. bm_interfaces // network information of bare-metal nodes
5.
On Aug 14, 2012, at 10:52 PM, Kurt Scholtens burnbrigh...@hotmail.com wrote:
Vish -
Thank you for responding. So, when using multiple interfaces, will setting
the PUBLIC_INTERFACE to the separate interface w/o VLANing work? Is that
what you are saying below? Are any additional
On Aug 14, 2012, at 10:00 PM, Chuck Thier cth...@gmail.com wrote:
snip
I could get behind this, and was was brought up by others in our group
as a more feasible short term solution. I have a couple of concerns
with this. It may cause just as much confusion if the api can't
reliably
Hi Anne,
I accidentally found this email of yours while looking for links to my post.
I'd probably have found it earlier if you cc'd me on
ekirpic...@gmail.com or ekirpic...@mirantis.com [yes, that's two
different spellings...] :)
I support the idea that this should be somehow integrated in the
Hi Eugene -
But I thought everyone was on the openstack list! :) Thanks for following up.
On Wed, Aug 15, 2012 at 4:35 PM, Eugene Kirpichov ekirpic...@gmail.com wrote:
Hi Anne,
I accidentally found this email of yours while looking for links to my post.
I'd probably have found it earlier if
I am interested in finding a solution that enables bare-metal and
virtualized requests to be serviced through the same scheduler where the
compute_nodes table has a full view of schedulable resources. This would
seem to simplify the end-to-end flow while opening up some additional use
cases
On Aug 15, 2012, at 3:17 PM, Michael J Fork mjf...@us.ibm.com wrote:
I am interested in finding a solution that enables bare-metal and virtualized
requests to be serviced through the same scheduler where the compute_nodes
table has a full view of schedulable resources. This would seem to
Hi Vish,
Is this discussion for long-term goal or for this Folsom release?
We still believe that bare-metal database is needed
because there is not an automated way how bare-metal nodes report their
capabilities
to their bare-metal nova-compute node.
Thanks,
David
I am interested
This was an immediate goal, the bare-metal nova-compute node could keep an
internal database, but report capabilities through nova in the common way with
the changes below. Then the scheduler wouldn't need access to the bare metal
database at all.
On Aug 15, 2012, at 4:23 PM, David Kang
I see.
We (NTT and USC/ISI) will discuss more about that.
And we will implement according to your input.
From now, we assume to use current db.
Here are my understanding of your comment. Please correct me if it is not
correct.
a) is clear.
b) NTT Docomo has implemented some features that
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/394/Project:quantal_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 04:01:56 -0400Build duration:6 min 2 secBuild cause:Started by an SCM changeBuilt
hed at 20120
at 20120815-0635Build needed 00:00:55, 9716k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/395/Project:quantal_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 08:23:32 -0400Build duration:5 min 42 secBuild cause:Started by user zulBuilt
at 20120815
at 20120815
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/404/Project:precise_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 10:01:54 -0400Build duration:7 min 19 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/397/Project:quantal_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 10:01:56 -0400Build duration:1 hr 48 minBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_trunk/44/Project:precise_folsom_cinder_trunkDate of build:Wed, 15 Aug 2012 12:01:55 -0400Build duration:1 min 40 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_horizon_trunk/91/Project:precise_folsom_horizon_trunkDate of build:Wed, 15 Aug 2012 12:31:56 -0400Build duration:2 min 24 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_cinder_trunk/48/Project:quantal_folsom_cinder_trunkDate of build:Wed, 15 Aug 2012 12:01:54 -0400Build duration:37 minBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/398/Project:quantal_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 12:31:57 -0400Build duration:15 minBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/405/Project:precise_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 12:34:21 -0400Build duration:13 minBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_quantum_trunk/105/Project:precise_folsom_quantum_trunkDate of build:Wed, 15 Aug 2012 13:01:53 -0400Build duration:1 min 41 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/401/Project:quantal_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 13:31:52 -0400Build duration:7 min 37 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_cinder_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_cinder_trunk/49/Project:quantal_folsom_cinder_trunkDate of build:Wed, 15 Aug 2012 14:02:02 -0400Build duration:6 min 17 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/402/Project:quantal_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 14:18:15 -0400Build duration:18 minBuild cause:Started by user zulBuilt on:pkg-builderHealth
at 20120815-1446Build needed 00:02:02, 63980k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d
Title: precise_folsom_horizon_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_horizon_trunk/92/Project:precise_folsom_horizon_trunkDate of build:Wed, 15 Aug 2012 15:01:54 -0400Build duration:4 min 12 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_horizon_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_horizon_trunk/95/Project:quantal_folsom_horizon_trunkDate of build:Wed, 15 Aug 2012 15:01:55 -0400Build duration:4 min 23 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_cinder_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_trunk/46/Project:precise_folsom_cinder_trunkDate of build:Wed, 15 Aug 2012 16:01:53 -0400Build duration:3 min 40 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_quantum_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_quantum_trunk/106/Project:precise_folsom_quantum_trunkDate of build:Wed, 15 Aug 2012 16:31:54 -0400Build duration:4 min 45 secBuild cause:Started by an SCM changeBuilt
at 20120815
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/403/Project:quantal_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 17:31:59 -0400Build duration:8 min 24 secBuild cause:Started by an SCM changeBuilt
at 20120815-1742Build needed 00:01:59, 63992k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d
Title: precise_essex_horizon_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_horizon_stable/20/Project:precise_essex_horizon_stableDate of build:Wed, 15 Aug 2012 20:20:58 -0400Build duration:2 min 6 secBuild cause:Started by user adamBuilt
at 20120815
at 20120815-2047Build needed 00:00:00, 0k disc
Title: precise_essex_horizon_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_horizon_stable/22/Project:precise_essex_horizon_stableDate of build:Wed, 15 Aug 2012 20:49:25 -0400Build duration:3 min 52 secBuild cause:Started by user adamBuilt
on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesNo ChangesConsole Output[...truncated 4142 lines...]Finished at 20120815-2107Build needed 00:04:06, 14320k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/essex-stable-testinggpg
Title: precise_essex_nova_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_nova_stable/37/Project:precise_essex_nova_stableDate of build:Wed, 15 Aug 2012 20:59:59 -0400Build duration:18 minBuild cause:Started by user adamBuilt on:pkg-builderHealth
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/405/Project:quantal_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 21:11:39 -0400Build duration:6 min 26 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/406/Project:quantal_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 21:37:07 -0400Build duration:5 min 27 secBuild cause:Started by an SCM changeBuilt
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/407/Project:quantal_folsom_nova_trunkDate of build:Wed, 15 Aug 2012 22:07:29 -0400Build duration:6 min 37 secBuild cause:Started by an SCM changeBuilt
at 20120815
51 matches
Mail list logo
