Re: [Openstack] need help on swift and python

[Christophe Le Guern]

Hi Yogesh,

Here is an example using swauth middleware and swift:

**
from cloudfiles.connection import Connection

conn = Connection("account:user", "password",
authurl="https://SWIFT-URL/auth/v1.0";)

container = conn.create_container("mycontainer")

obj = container.create_object("myobject.txt")
obj.content_type = "text/plain"
obj.write("Hello World")
**

Christophe

On Tue, Jun 26, 2012 at 7:14 AM, Yogesh Bansal  wrote:
> Hi,
>
>
>
> I want to upload a file or image on swift object storage server.  I can do
> it using curl command. But I am not able to do it using python apis. I am
> using Django and python to make web based application, which required to
> store file from client to swift object storage server.
>
>
>
> Is there any swift  and python experts, who can guide me in this regard.
>
>
>
> I am able to create and list containers using python.
>
>
>
> An example will be very helpful.
>
>
>
>
>
>
>
>
>
>
>
> Thanks
>
> Yogesh Bansal
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Openstack Command Line

[Vaze, Mandar]

http://lmgtfy.com/?q=openstack+command+line+tools

-Mandar

From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net 
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On 
Behalf Of Trinath Somanchi
Sent: Tuesday, June 26, 2012 10:49 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] Openstack Command Line

Hi-

With out using Horizon, is there any command line Openstack for configuring and 
bringing up instances?



--
Regards,
--
Trinath Somanchi,
+91 9866 235 130


__
Disclaimer:This email and any attachments are sent in strictest confidence for 
the sole use of the addressee and may contain legally privileged, confidential, 
and proprietary data.  If you are not the intended recipient, please advise the 
sender by replying promptly to this email and then delete and destroy this 
email and any attachments without any further use, copying or forwarding
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Openstack Command Line

[Atul Jha]

Hi Trinath,
Checking docs.opestack.org will help, look for nova related commands.


Cheers!!

Atul

From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net 
[openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of 
Trinath Somanchi [trinath.soman...@gmail.com]
Sent: Tuesday, June 26, 2012 10:48 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] Openstack Command Line

Hi-

With out using Horizon, is there any command line Openstack for configuring and 
bringing up instances?



--
Regards,
--
Trinath Somanchi,
+91 9866 235 130

http://www.csscorp.com/common/email-disclaimer.php
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Openstack Command Line

[Matt Joyce]

yes there is.  check out the python-novaclient, or use euca2ools.

Cheers,

  Matt

On Mon, Jun 25, 2012 at 10:18 PM, Trinath Somanchi <
trinath.soman...@gmail.com> wrote:

> Hi-
>
> With out using Horizon, is there any command line Openstack for
> configuring and bringing up instances?
>
>
>
> --
> Regards,
> --
> Trinath Somanchi,
> +91 9866 235 130
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Openstack Command Line

[Trinath Somanchi]

Hi-

With out using Horizon, is there any command line Openstack for configuring
and bringing up instances?



-- 
Regards,
--
Trinath Somanchi,
+91 9866 235 130
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] need help on swift and python

[Yogesh Bansal]

Hi,
 
I want to upload a file or image on swift object storage server.  I can do
it using curl command. But I am not able to do it using python apis. I am
using Django and python to make web based application, which required to
store file from client to swift object storage server.
 
Is there any swift  and python experts, who can guide me in this regard.
 
I am able to create and list containers using python. 
 
An example will be very helpful.
 
 
 
 
 
Thanks
Yogesh Bansal
 
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [nova][ec2] EC2 CreateImage API and nova boot-from-volume

[Scott Moser]

On Mon, 25 Jun 2012, Vishvananda Ishaya wrote:

>
> On Jun 25, 2012, at 9:25 AM, Eoghan Glynn wrote:
>
> >
> > Hi Folks,
> >
> > I've been looking into the (currently broken) EC2 CreateImage API support
> > and just wanted to get a sanity check on the following line of reasoning:
> >
> > - EC2 CreateImage should *only* apply to booted-from-volume nova servers,
> >  for fidelity with the EC2 limitation to EBS-based instances (i.e. should
> >  raise InvalidParameterValue when the API is applied to an instance-store
> >  style server).
> >
> >  So my previous crack at this https://review.openstack.org/8532
> >  was going completely in the wrong direction.
> >
> > - Normally, a snapshot of a bootable-volume is booted via the native API
> >  tooling with something like:
> >
> >nova boot --image IMAGE_ID --block-device-mapping 
> > vd[a-z]=SNAP_ID:snap::0 ...
> >
> >  where AFAICS the IMAGE_ID is *only* used to determine the kernel and
> >  ramdisk IDs and is otherwise irrelevant.
> >
> > - The EC2 CreateImage on the other hand requires that a usable image ID
> >  be returned, not set of a volume snapshot IDs.
> >
> > - The resulting image should be bootable via EC2 RunInstances, but doesn't
> >  necessarily need to be portable, as it depends on local snapshot ID(s).
> >
> > Here a few different potential approaches to the creation of this image:
> >
> > 1. Create a "place-holder" image in glance with the image data being
> >   effectively empty, and the following properties set:
> >
> > * the imaged instance's kernel and ramdisk IDs
> > * block device mapping containing the appropriate snapshot ID(s)
> >
> >   so that we can boot from this image without providing additional
> >   context (such as the via nova boot --block-device-mapping option)
> >
>
> This looks like the best option to me, since we are already storing bdm 
> information in
> images already.

This feels to me like how it is implemented in EC2.  Essentially the
when you RegisterImage with a snapshot rather than a manifest, you
basically get an image-id that refers to a block-device mapping
referencing a snapshot.

I guess more indirectly the same is true about "instance store images".
Ie,
  instance-store ami:
   * root-device: S3://some-bucket/some.manifest
   * root-device-type: instance-store
   * name
   * kernel, ramdisk
   ...
  ebsoroot ami:
   * root-device: snapshot:snap-abcdefg
   * root-device-type: ebs
   * name
   * kernel, ramdisk
   ...

The run-instance code then just knows that if a block device mapping
references an S3 manifest, it needs to populate a "instance-store" root
disk with the content from the manifest.

Do we use the S3 manifest for anything other than the initial copy to
glance?

> > 2. Extend the s3_image mapping logic such that an ami-* style ID can be
> >   mapped directly to a set of properties, snapshot IDs etc (so there
> >   would no image registration with glance).
>
> Rather not have to keep track of this stuff in the mapping layer, but we may 
> end up
> having to keep more data there eventually.

Or, turn the s3_image mapping into something that fits with the
volume-based root.

> > - How should the lifecycle of the image and the corresponding
> >  snapshot(s) be intertwined? (e.g. should a deletion of the snapshot
> >  cause the corresponding image to be also deleted or marked
> >  unusable?)
>
> That sounds a bit complicated. We may just have to fail when the image is 
> launched

Just for reference, against EC2:
$ euca-register --snapshot snap-3324e74d --name "smoser.foo"
IMAGE ami-c0c865a9
$ euca-delete-snapshot snap-3324e74d
InvalidSnapshot.InUse: The snapshot snap-3324e74d is currently in use by 
ami-c0c865a9

So what happens on EC2 (which would also seem reasonably simple to
implement) is that the request to delete the snapshot fails if there is an
image with that snapshot registered.

> > - Would a corresponding feature for the native API make sense?
> >  i.e. an equivalent of the nova createImage action that does not
> >  depend on the qemu-img command, but instead works for booted-from-vol
> >  servers. This would avoid the counter-intuitive use of an imageRef
> >  that's only used to grab the kernel and ramdisk IDs.
>
> I think this makes sense, but I think we should remove the requirement for 
> imageRef
> regardless.
>
> This whole cluster is due to the organic nature of aws moving from regular 
> images
> to ebs based images and gradually adding options. We are essentially having
> to map to a badly designed api, but I think your approach is reasonable.

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Swift] rsyslog daemon reloading causes swift related services hangs and CPU reach to 100%

[MORITA Kazutaka]

At Sat, 23 Jun 2012 14:09:43 +0800,
Kuo Hugo wrote:
> 
> nice suggestion ,
> We decide to use UPD now

Just an FYI, the fix was merged into upstream python.

http://hg.python.org/cpython/rev/6af0535b5e3a

Thanks,

Kazutaka

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] big problem with boot from iso

[William Herry]

Hi
I use boot from iso to install a centos instance, it can't recognize the
disk, I create a flavor with 300G ephemeral and 300G disk, it says no valid
disk found, but when I create a flavor with 30 swap, it found the disk
vdb, and can install the system, but of course can boot

can some one tell me what's going go,

-- 



William Herry

williamherrych...@gmail.com
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] New mailing list server [status update]

[Stefano Maffulli]

Hello folks,

we're getting closer to being able to have a new mailing list manager.
Duncan and the infra team have a new machine running, with mailman
installed. We tested also the migration of the archives, successfully.

You can have a look at the result on the staging server:

http://stagelists.openstack.org/cgi-bin/mailman/listinfo/

Notice the visual appearance of the individual lists, like

http://stagelists.openstack.org/cgi-bin/mailman/listinfo/foundation

and of the archives (only visible at the url below):

http://stagelists.openstack.org/pipermail/openstack-dev/

I think it's good to give users landing on the archives an easy way to
navigate to openstack.org and to our others site, like wiki and docs to
get more information about openstack.

Please give the site a fast spin when you have time and let us know if
it doesn't work for you.

The next step is to migrate all the lists from lists.openstack.org
(operators@ is there) to the new server. Once that is done and stable we
should also think about what to do with the other lists.

cheers,
stef

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [metering] collector storage backends

[Doug Hellmann]

After running some numbers through the calculator Nick put together, we're
comfortable starting with a MongoDB backend for the monitoring data. I know
a couple of other people were interested in that, but we decided to go with
the SQLAlchemy backend at least in part because I was advocating that.

I plan to start working on the MongoDB plugin this week, since I anticipate
that getting us to something "useful" more quickly than going with
SQLAlchemy. If you have any objections, let me know.

Doug
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [nova] RFC - filtering compute nodes in a mixed environment

[Jim Fehlig]

In a previous thread [1], I mentioned two possibilities for controlling
the scheduling of instances to an appropriate compute node in a mixed
node (Xen, KVM) environment.  The first approach uses availability
zones, the second uses the existing vm_mode image property.  Folks
seemed to agree on the latter, and the attached patch adds a check to
the compute filter to ensure the compute node can accommodate the
instance type.

The compute filter seems like the right place to add this check, but
posting as a RFC since I'm not sure if this would be agreeable to
everyone as compared to a custom filter for example.

Regards,
Jim

[1]
http://openstack.markmail.org/search/?q=improve%20xen#query:improve%20xen+page:1+mid:knmnylknf2imnruy+state:results

>From bb8777a415d5db22b83971357882261fbef092a9 Mon Sep 17 00:00:00 2001
From: Jim Fehlig 
Date: Mon, 25 Jun 2012 15:54:43 -0600
Subject: [PATCH] Add check for vm_mode in compute filter

Add a check in the scheduler compute filter to see if the compute service
supports the vm_mode specified in the instance properties.

As mentioned in a previous thread [1], there needs to be a way to control
scheduling of instances to an appropriate node in a mixed compute node
environment.  The existing vm_mode property, in conjuction with the
additional_compute_capabilities flag, provides a mechanism to filter
appropriate nodes.

[1] http://openstack.markmail.org/search/?q=improve%20xen#query:improve%20xen+page:1+mid:knmnylknf2imnruy+state:results
---
 nova/scheduler/filters/compute_filter.py  |   20 +++-
 nova/tests/scheduler/test_host_filters.py |   26 ++
 2 files changed, 45 insertions(+), 1 deletion(-)

diff --git a/nova/scheduler/filters/compute_filter.py b/nova/scheduler/filters/compute_filter.py
index 5409d3d..5187c39 100644
--- a/nova/scheduler/filters/compute_filter.py
+++ b/nova/scheduler/filters/compute_filter.py
@@ -22,7 +22,8 @@ LOG = logging.getLogger(__name__)
 
 
 class ComputeFilter(filters.BaseHostFilter):
-"""HostFilter hard-coded to work with InstanceType records."""
+"""HostFilter hard-coded to work with InstanceType and
+InstanceProperties records."""
 
 def _satisfies_extra_specs(self, capabilities, instance_type):
 """Check that the capabilities provided by the compute service
@@ -38,8 +39,21 @@ class ComputeFilter(filters.BaseHostFilter):
 return False
 return True
 
+def _satisfies_capabilities(self, capabilities, instance_props):
+"""Check that the capabilities provided by the compute service
+satisfies properties defined in the instance."""
+vm_mode = instance_props.get('vm_mode')
+if not vm_mode:
+return True
+if capabilities.get(vm_mode, None):
+return True
+else:
+return False
+
 def host_passes(self, host_state, filter_properties):
 """Return a list of hosts that can create instance_type."""
+spec = filter_properties.get('request_spec', {})
+instance_props = spec.get('instance_properties', {})
 instance_type = filter_properties.get('instance_type')
 if host_state.topic != 'compute' or not instance_type:
 return True
@@ -57,4 +71,8 @@ class ComputeFilter(filters.BaseHostFilter):
 LOG.debug(_("%(host_state)s fails instance_type extra_specs "
 "requirements"), locals())
 return False
+if not self._satisfies_capabilities(capabilities, instance_props):
+LOG.debug(_("%(host_state)s fails instance_properties "
+"requirements"), locals())
+return False
 return True
diff --git a/nova/tests/scheduler/test_host_filters.py b/nova/tests/scheduler/test_host_filters.py
index 80da5ac..3a99292 100644
--- a/nova/tests/scheduler/test_host_filters.py
+++ b/nova/tests/scheduler/test_host_filters.py
@@ -349,6 +349,32 @@ class HostFiltersTestCase(test.TestCase):
 
 self.assertFalse(filt_cls.host_passes(host, filter_properties))
 
+def test_compute_filter_passes_additional_caps(self):
+self._stub_service_is_up(True)
+filt_cls = self.class_map['ComputeFilter']()
+req_spec = {'instance_properties': {'vm_mode': 'pv'}}
+capabilities = {'enabled': True, 'pv': True, 'hvm': True}
+service = {'disabled': False}
+filter_properties = {'instance_type': {'memory_mb': 1024},
+ 'request_spec' : req_spec}
+host = fakes.FakeHostState('host1', 'compute',
+{'free_ram_mb': 1024, 'capabilities': capabilities,
+ 'service': service})
+self.assertTrue(filt_cls.host_passes(host, filter_properties))
+
+def test_compute_filter_fails_additional_caps(self):
+self._stub_service_is_up(True)
+filt_cls = self.class_map['ComputeFilter']()
+req_spec = {'instance_properties': {'vm_mode': 'pv'}}
+capabilities = {'

Re: [Openstack] UnifiedCLI suggestion

[Doug Hellmann]

On Mon, Jun 25, 2012 at 6:19 PM, Ken Thomas  wrote:

> Greetings all,
>
> Our security folks have an issue with putting passwords on the command
> line or in the environment. I wrote up a blueprint that gives the details
> on their objections as well as a proposed short-term fix for keystone (
> https://blueprints.launchpad.**net/keystone/+spec/prompt-for-**password).
> We'd like to see this same change get into UnifiedCLI as a longer term fix.
>
> The change is minor.  If no password was found on the command line or in
> the env, just before the "expecting password" error is raised, we make an
> attempt to prompt the user for it.  If we get something, great! Our
> security folks are happy and we keep processing.  If we don't get the
> password for any number of reasons (keystone wasn't being run from a tty,
> the user hit Ctrl-C or Ctrl-D when prompted), then we raise the error just
> as before.
>
> I've already submitted the keystone changes for review (
> https://review.openstack.org/**#/c/8958/3/keystoneclient/**shell.py)
> and I'd be happy to make the same change to UnifiedCLI as well.
>

Thanks, Ken! That sounds like a good change to make. If you add me as a
reviewer on the patch, I'll make sure to look at the changes.

Doug
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] UnifiedCLI suggestion

[Ken Thomas]

Greetings all,

Our security folks have an issue with putting passwords on the command 
line or in the environment. I wrote up a blueprint that gives the 
details on their objections as well as a proposed short-term fix for 
keystone 
(https://blueprints.launchpad.net/keystone/+spec/prompt-for-password). 
We'd like to see this same change get into UnifiedCLI as a longer term fix.


The change is minor.  If no password was found on the command line or in 
the env, just before the "expecting password" error is raised, we make 
an attempt to prompt the user for it.  If we get something, great! Our 
security folks are happy and we keep processing.  If we don't get the 
password for any number of reasons (keystone wasn't being run from a 
tty, the user hit Ctrl-C or Ctrl-D when prompted), then we raise the 
error just as before.


I've already submitted the keystone changes for review 
(https://review.openstack.org/#/c/8958/3/keystoneclient/shell.py) and 
I'd be happy to make the same change to UnifiedCLI as well.


Thanks!

Ken






___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [metering] need code review for bug #1005941 (emitting "exists" events)

[Doug Hellmann]

I have a small patch to emit metering data for existing instances when they
are polled for CPU utilization.

https://review.stackforge.org/#/c/237/

Doug
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [nova][ec2] EC2 CreateImage API and nova boot-from-volume

[Vishvananda Ishaya]

On Jun 25, 2012, at 9:25 AM, Eoghan Glynn wrote:

> 
> Hi Folks,
> 
> I've been looking into the (currently broken) EC2 CreateImage API support 
> and just wanted to get a sanity check on the following line of reasoning:
> 
> - EC2 CreateImage should *only* apply to booted-from-volume nova servers,
>  for fidelity with the EC2 limitation to EBS-based instances (i.e. should
>  raise InvalidParameterValue when the API is applied to an instance-store
>  style server). 
> 
>  So my previous crack at this https://review.openstack.org/8532
>  was going completely in the wrong direction.
> 
> - Normally, a snapshot of a bootable-volume is booted via the native API
>  tooling with something like:
> 
>nova boot --image IMAGE_ID --block-device-mapping vd[a-z]=SNAP_ID:snap::0 
> ...
> 
>  where AFAICS the IMAGE_ID is *only* used to determine the kernel and
>  ramdisk IDs and is otherwise irrelevant.
> 
> - The EC2 CreateImage on the other hand requires that a usable image ID
>  be returned, not set of a volume snapshot IDs.
> 
> - The resulting image should be bootable via EC2 RunInstances, but doesn't
>  necessarily need to be portable, as it depends on local snapshot ID(s).
> 
> Here a few different potential approaches to the creation of this image:
> 
> 1. Create a "place-holder" image in glance with the image data being
>   effectively empty, and the following properties set:
> 
> * the imaged instance's kernel and ramdisk IDs
> * block device mapping containing the appropriate snapshot ID(s)
> 
>   so that we can boot from this image without providing additional
>   context (such as the via nova boot --block-device-mapping option)
> 

This looks like the best option to me, since we are already storing bdm 
information in
images already.

> 2. Extend the s3_image mapping logic such that an ami-* style ID can be
>   mapped directly to a set of properties, snapshot IDs etc (so there
>   would no image registration with glance).

Rather not have to keep track of this stuff in the mapping layer, but we may 
end up
having to keep more data there eventually.

> 
> 3. Construct an AMI manifest containing the appropriate blockDeviceMapping
>   and then leverage EC2 RegisterImage logic to create an AMI image.

It looks like they are just parsed into image metadata information anyway so I 
don't see the point
of munging back and forth through xml

> 
> Some questions:
> 
> - Does any of the above approaches to the image creation make sense?
> 
>  Option #3 in particular seems uneccessarily complex to me, and would
>  I think require some reverse-engineering of the manifest format. I'm
>  not sure there's much benefit in aping the EC2 image bundling/
>  registration approach given that the resulting image wouldn't be
>  portable outside the current openstack deployment. However I may be
>  missing something there ...

Agreed, too complicated IMO

> 
> - How should the lifecycle of the image and the corresponding
>  snapshot(s) be intertwined? (e.g. should a deletion of the snapshot
>  cause the corresponding image to be also deleted or marked
>  unusable?)

That sounds a bit complicated. We may just have to fail when the image is 
launched
> 
> - Would a corresponding feature for the native API make sense? 
>  i.e. an equivalent of the nova createImage action that does not
>  depend on the qemu-img command, but instead works for booted-from-vol
>  servers. This would avoid the counter-intuitive use of an imageRef
>  that's only used to grab the kernel and ramdisk IDs.

I think this makes sense, but I think we should remove the requirement for 
imageRef
regardless.

This whole cluster is due to the organic nature of aws moving from regular 
images
to ebs based images and gradually adding options. We are essentially having
to map to a badly designed api, but I think your approach is reasonable.

Vish


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] Multi-host ip mix up.

[Vishvananda Ishaya]

10.0.9.5 is probably the ip that nova assigned to your compute host for the 
bridge.

ip addr show should show it on br100

There is likely something else going on that is causing your instance to fail 
to network properly. I would check the console output of the vm first, make 
sure it is getting an ip address. If that looks good, check for security group 
rules, then start doing tcpdump to see where you are losing packets.

Vish

On Jun 25, 2012, at 9:08 AM, Leander Bessa Beernaert wrote:

> Hello, 
> 
> I've setup OpenStack with a multi-host configuration. Everything appears to 
> be working fine. However, when i launch an instance, it get's assigned an ip 
> (10.0.9.3) and when i ping that IP i get this output:
> ping 10.0.9.3
> PING 10.0.9.3 (10.0.9.3) 56(84) bytes of data.
> >From 10.0.9.5 icmp_seq=1 Destination Host Unreachable
> From 10.0.9.5 icmp_seq=2 Destination Host Unreachable
> From 10.0.9.5 icmp_seq=3 Destination Host Unreachable
> 
> If i ping the adress 10.0.9.5 i get a response.
> 
>  ping 10.0.9.5
> PING 10.0.9.5 (10.0.9.5) 56(84) bytes of data.
> 64 bytes from 10.0.9.5: icmp_req=1 ttl=64 time=0.043 ms
> 64 bytes from 10.0.9.5: icmp_req=2 ttl=64 time=0.035 ms
> 64 bytes from 10.0.9.5: icmp_req=3 ttl=64 time=0.036 ms
> 
> Any idea what's happening here?
> 
> Regards,
> Leander
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Noob question about api client access

[Roman Sokolkov]

Hi! You could also see on endpoints in keystone. And satisfy that urls
differ from localhost.

keystone endpoint-list

As I remember.

Thanks, Roman S.
24.06.2012 19:15 пользователь "Jonathan Proulx"  написал:

> Hi All,
>
> I have a shiny new install of openstack and from the controller node
> (the one with keystone, glance, horizon and all the nova pieces) I can
> run everything as I expect using the "nova" cli tools upload images
> boot instances manage the network, etc.  I can also use the Horizon
> wed interface from remote systems just fine (of course all the actual
> commands are run locally on the controller)
>
> Where it get weird is when I try to use the "nova" cli on a remote
> client.  Using the same "openrc" to set up the environment "nova
> credentials" returns the expected result but all the other commands
> I've tried (mostly of the "list" variety) fail like this:
>
> $ nova list
> ERROR: n/a (HTTP 400)
>
>
> The install is Essex on Ubuntu Precise which I deployed using the
> Puppet OpenStack module.  The example config puppet deployed for me
> was only listening on 127.0.0.1 so I had to change the "bind_host" in
> /etc/keystone/keystone.conf from 127.0.0.1 to 0.0.0.0 to get the 'nova
> credentials' to run.  I've been sifting through the "OpenStack Compute
> Starter Guide" and greping for and replacing references to localhost
> or 127.0.0.1 in the various configs I alsoe tried adding
> "--allow_admin_api=true" to the nova.conf which was in the openstack
> docs but not in my conf,  but I'm clearly still missing something.
>
> Hopefully this is obvious to some one more familiar with all the pieces?
>
> Thanks,
> -Jon
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Ceph as a NOVA-INST-DIR/instances/ storage backend

[Igor Laskovy]

Thank you Florian and Tommi, I appreciated your help))

On Mon, Jun 25, 2012 at 8:18 PM, Tommi Virtanen  wrote:
> On Mon, Jun 25, 2012 at 10:03 AM, Igor Laskovy  wrote:
>> but can I use RBD for booting instances? I would like store whole VM on the
>> Ceph, not only persistent volumes (actually for my project I not prefer use
>> persistent volumes at all).
>
> OpenStack Essex does not make it convenient, but it can boot off of RBD.
>
> We don't have really good documentation on that yet, but the relevant
> resources are:
>
> https://github.com/ceph/ceph-openstack-tools/blob/master/boot-from-volume
> https://github.com/ceph/ceph-openstack-tools/blob/master/start-on-rbd.sh
> http://docs.openstack.org/trunk/openstack-compute/admin/content/boot-from-volume.html



-- 
Igor Laskovy
facebook.com/igor.laskovy
Kiev, Ukraine

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] Snapshot stuck in Queued state, no erros found in compute log

[Vishvananda Ishaya]

Usually queued means it didn't ever get uploaded into glance. Any errors in the 
glance log? I have never seen the error below, but it could be related.

Vish

On Jun 25, 2012, at 3:50 AM, Leander Bessa Beernaert wrote:

> Hello,
> 
> I've performed snapshots over and over without ever running into trouble, 
> however now one of them is stuck in the Queued state. I've searched the 
> machine's compute.log for any indication of an error, but nothing showed up. 
> I did a quick search and usually the erros appear in the compute.log or the 
> libivirtd.log. The only thing i found in the libvirtd.log were these two 
> lines:
> 
> 2012-06-25 10:37:05.957+: 6830: warning : qemuCapsInit:856 : Failed to 
> get host power management capabilities
> 2012-06-25 10:37:06.612+: 6831: error : virExecWithHook:328 : Cannot find 
> 'pm-is-supported' in path: No such file or director
>  
> Could that be the problem?
> 
> Regards,
> Leander
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] No tests available in custom branch

[Kevin L. Mitchell]

On Mon, 2012-06-25 at 16:56 +0100, Leander Bessa Beernaert wrote:
> Here's the diff http://paste.openstack.org/show/18756/

Change "import diagnostics" to "from nova.virt.libvirt import
diagnostics".  (Also note that you may need to add a space between your
name and your email address in Authors, and if you mean to submit this
to the trunk, it'd be nice to put your entry in the
alphabetically-appropriate place…)
-- 
Kevin L. Mitchell 


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] AttributeError: "virDomain instance has no attribute 'reset'"

[Dan Prince]

I went ahead and implemented the fix here:

https://review.openstack.org/#/c/8943/1/nova/virt/libvirt/connection.py

Once we do this the version requirement should be back at 0.9.6 (I think).

Dan

- Original Message -
> From: "Jay Pipes" 
> To: openstack@lists.launchpad.net
> Sent: Friday, June 22, 2012 12:13:07 PM
> Subject: Re: [Openstack] AttributeError: "virDomain instance has no attribute 
> 'reset'"
> 
> That's pretty much what I understood based on a conversation with
> Vish
> on IRC the other day. It's caused me to pretty much give up on 11.10
> for
> modern OpenStack (Nova) installs.
> 
> -jay
> 
> On 06/22/2012 01:23 AM, Vaze, Mandar wrote:
> > Found this bug (albeit for Fedora 16)
> > https://bugs.launchpad.net/nova/+bug/1011863
> > 
> >
> > I’ve updated the bug with my details
> >
> > Does that mean Folsom won’t be supported on Ubuntu 11.10 ?
> >
> > -Mandar
> >
> > *From:*openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
> > [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net]
> > *On Behalf Of *Vaze, Mandar
> > *Sent:* Friday, June 22, 2012 9:41 AM
> > *To:* Vishvananda Ishaya
> > *Cc:* openstack@lists.launchpad.net
> > *Subject:* Re: [Openstack] AttributeError: "virDomain instance has
> > no
> > attribute 'reset'"
> >
> > Vish,
> >
> > I’m running on Ubuntu 11.10 (GNU/Linux 3.0.0-12-server x86_64)
> >
> > When I tried to upgrade I got the following message
> >
> > libvirt-bin is already the newest version.
> >
> > libvirt0 is already the newest version.
> >
> > python-libvirt is already the newest version.
> >
> > Which package should I upgrade/install ?
> >
> > Thanks,
> >
> > -Mandar
> >
> > *From:*Vishvananda Ishaya [mailto:vishvana...@gmail.com]
> > 
> > *Sent:* Friday, June 22, 2012 12:13 AM
> > *To:* Vaze, Mandar
> > *Subject:* Re: AttributeError: "virDomain instance has no attribute
> > 'reset'"
> >
> > the reset command was only recently added to libvirt, so your
> > version is
> > probably just to old. We have discussed adding a fallback of
> > shutting
> > down and restarting the domain if reset is not defined, but no one
> > has
> > implemented it yet.
> >
> > Vish
> >
> > On Jun 21, 2012, at 5:56 AM, Vaze, Mandar wrote:
> >
> > Vish,
> >
> > I recently merged my code with master after a few weeks.
> >
> > Now I’m getting the error mentioned in the subject line during
> > reboot.
> >
> > I looked at the history and this change is done in the following
> > commit
> > by you.
> >
> > https://github.com/openstack/nova/commit/ae878fc8b9761d099a4145617e4a48cbeb390623
> >
> > I also realized that you have defined reset() method in fakelibvirt
> > for
> > testing - so may be tests pass OK.
> >
> > I’m using libvirt_type=kvm
> >
> > Do I need to update any library (python or otherwise) for this
> > change ?
> >
> > Any other suggestions to troubleshoot this ?
> >
> > Thanks,
> >
> > -Mandar
> >
> > Here is relevant snippet from my debug session :
> >
> >>  /opt/stack/nova/nova/virt/libvirt/connection.py(847)_hard_reboot()
> >
> > -> virt_dom.reset(0)
> >
> > (Pdb) dir(virt_dom)
> >
> > ['ID', 'OSType', 'UUID', 'UUIDString', 'XMLDesc', '__del__',
> > '__doc__',
> > '__init__', '__module__', '_conn', '_o', 'abortJob',
> > 'attachDevice',
> > 'attachDeviceFlags', 'autostart', 'blkioParameters', 'blockInfo',
> > 'blockPeek', 'blockStats', 'connect', 'coreDump', 'create',
> > 'createWithFlags', 'destroy', 'detachDevice', 'detachDeviceFlags',
> > 'hasCurrentSnapshot', 'hasManagedSaveImage', 'info', 'injectNMI',
> > 'interfaceStats', 'isActive', 'isPersistent', 'isUpdated',
> > 'jobInfo',
> > 'managedSave', 'managedSaveRemove', 'maxMemory', 'maxVcpus',
> > 'memoryParameters', 'memoryPeek', 'memoryStats', 'migrate',
> > 'migrate2',
> > 'migrateSetMaxDowntime', 'migrateSetMaxSpeed', 'migrateToURI',
> > 'migrateToURI2', 'name', 'openConsole', 'pinVcpu', 'reboot',
> > 'resume',
> > 'revertToSnapshot', 'save', 'schedulerParameters',
> > 'schedulerParametersFlags', 'schedulerType', 'screenshot',
> > 'setAutostart', 'setBlkioParameters', 'setMaxMemory', 'setMemory',
> > 'setMemoryFlags', 'setMemoryParameters', 'setSchedulerParameters',
> > 'setSchedulerParametersFlags', 'setVcpus', 'setVcpusFlags',
> > 'shutdown',
> > 'snapshotCreateXML', 'snapshotCurrent', 'snapshotListNames',
> > 'snapshotLookupByName', 'snapshotNum', 'state', 'suspend',
> > 'undefine',
> > 'updateDeviceFlags', 'vcpus', 'vcpusFlags']
> >
> > (Pdb) type( virt_dom)
> >
> > 
> >
> > (Pdb) type(virt_dom)
> >
> > 
> >
> > (Pdb) n
> >
> > AttributeError: "virDomain instance has no attribute 'reset'"
> >
> >
> > __
> > Disclaimer:This email and any attachments are sent in strictest
> > confidence for the sole use of the addressee and may contain
> > legally
> > privileged, confidential, and proprietary data. If you are not the
> > intended recipient, p

Re: [Openstack] Ceph as a NOVA-INST-DIR/instances/ storage backend

[Florian Haas]

On Mon, Jun 25, 2012 at 6:03 PM, Tommi Virtanen  wrote:
> On Sat, Jun 23, 2012 at 11:42 AM, Igor Laskovy  wrote:
>> Hi all from hot Kiev))
>>
>> Does anybody use Ceph as a backend storage for NOVA-INST-DIR/instances/ ?

Yes. http://www.sebastien-han.fr/blog/2012/06/10/introducing-ceph-to-openstack/
Look at the "Live Migration with CephFS" part.

>> Is it in production use?

"Production use" would require CephFS to be production ready, which at
this point it isn't.

> Live migration is still possible?

Yes.

>> I kindly ask any advice of best practices point of view.
>
> That's the shared NFS mount style for storing images, right? While you
> could use the Ceph Distributed File System for that, there's a better
> answer (for both Nova and Glance): RBD.

... which sort of goes hand-in-hand with boot from volume, which was
just recently documented in the Nova admin guide, so you may want to
take a look: 
http://docs.openstack.org/trunk/openstack-compute/admin/content/boot-from-volume.html

That being said, volume attachment persistence across live migrations
hasn't always been stellar in Nova, and I'm not 100% sure how well
trunk currently deals with that.

Cheers,
Florian

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Ceph as a NOVA-INST-DIR/instances/ storage backend

[Igor Laskovy]

Thank you Tommi,

but can I use RBD for booting instances? I would like store whole VM on the
Ceph, not only persistent volumes (actually for my project I not prefer use
persistent volumes at all).

Igor Laskovy
facebook.com/igor.laskovy
Kiev, Ukraine
On Jun 25, 2012 7:03 PM, "Tommi Virtanen"  wrote:

> On Sat, Jun 23, 2012 at 11:42 AM, Igor Laskovy 
> wrote:
> > Hi all from hot Kiev))
> >
> > Does anybody use Ceph as a backend storage for NOVA-INST-DIR/instances/ ?
> > Is it in production use? Live migration is still possible?
> > I kindly ask any advice of best practices point of view.
>
> That's the shared NFS mount style for storing images, right? While you
> could use the Ceph Distributed File System for that, there's a better
> answer (for both Nova and Glance): RBD.
>
> Our docs are still being worked on, but you can see the current state
> at http://ceph.com/docs/master/rbd/rbd-openstack/
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [nova][ec2] EC2 CreateImage API and nova boot-from-volume

[Eoghan Glynn]

Hi Folks,

I've been looking into the (currently broken) EC2 CreateImage API support 
and just wanted to get a sanity check on the following line of reasoning:

- EC2 CreateImage should *only* apply to booted-from-volume nova servers,
  for fidelity with the EC2 limitation to EBS-based instances (i.e. should
  raise InvalidParameterValue when the API is applied to an instance-store
  style server). 

  So my previous crack at this https://review.openstack.org/8532
  was going completely in the wrong direction.

- Normally, a snapshot of a bootable-volume is booted via the native API
  tooling with something like:

nova boot --image IMAGE_ID --block-device-mapping vd[a-z]=SNAP_ID:snap::0 
...

  where AFAICS the IMAGE_ID is *only* used to determine the kernel and
  ramdisk IDs and is otherwise irrelevant.

- The EC2 CreateImage on the other hand requires that a usable image ID
  be returned, not set of a volume snapshot IDs.

- The resulting image should be bootable via EC2 RunInstances, but doesn't
  necessarily need to be portable, as it depends on local snapshot ID(s).

Here a few different potential approaches to the creation of this image:

1. Create a "place-holder" image in glance with the image data being
   effectively empty, and the following properties set:

 * the imaged instance's kernel and ramdisk IDs
 * block device mapping containing the appropriate snapshot ID(s)

   so that we can boot from this image without providing additional
   context (such as the via nova boot --block-device-mapping option)

2. Extend the s3_image mapping logic such that an ami-* style ID can be
   mapped directly to a set of properties, snapshot IDs etc (so there
   would no image registration with glance).

3. Construct an AMI manifest containing the appropriate blockDeviceMapping
   and then leverage EC2 RegisterImage logic to create an AMI image.

Some questions:

- Does any of the above approaches to the image creation make sense?

  Option #3 in particular seems uneccessarily complex to me, and would
  I think require some reverse-engineering of the manifest format. I'm
  not sure there's much benefit in aping the EC2 image bundling/
  registration approach given that the resulting image wouldn't be
  portable outside the current openstack deployment. However I may be
  missing something there ...

- How should the lifecycle of the image and the corresponding
  snapshot(s) be intertwined? (e.g. should a deletion of the snapshot
  cause the corresponding image to be also deleted or marked
  unusable?)

- Would a corresponding feature for the native API make sense? 
  i.e. an equivalent of the nova createImage action that does not
  depend on the qemu-img command, but instead works for booted-from-vol
  servers. This would avoid the counter-intuitive use of an imageRef
  that's only used to grab the kernel and ramdisk IDs.

Cheers,
Eoghan

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack][Nova] Multi-host ip mix up.

[Leander Bessa Beernaert]

Hello,

I've setup OpenStack with a multi-host configuration. Everything appears to
be working fine. However, when i launch an instance, it get's assigned an
ip (10.0.9.3) and when i ping that IP i get this output:

> ping 10.0.9.3
> PING 10.0.9.3 (10.0.9.3) 56(84) bytes of data.
> From 10.0.9.5 icmp_seq=1 Destination Host Unreachable
> From 10.0.9.5 icmp_seq=2 Destination Host Unreachable
> From 10.0.9.5 icmp_seq=3 Destination Host Unreachable


If i ping the adress 10.0.9.5 i get a response.

 ping 10.0.9.5
> PING 10.0.9.5 (10.0.9.5) 56(84) bytes of data.
> 64 bytes from 10.0.9.5: icmp_req=1 ttl=64 time=0.043 ms
> 64 bytes from 10.0.9.5: icmp_req=2 ttl=64 time=0.035 ms
> 64 bytes from 10.0.9.5: icmp_req=3 ttl=64 time=0.036 ms


Any idea what's happening here?

Regards,
Leander
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] No tests available in custom branch

[Leander Bessa Beernaert]

Here's the diff http://paste.openstack.org/show/18756/

On Mon, Jun 25, 2012 at 4:53 PM, Brian Waldon wrote:

> I usually run into this kind of problem when I break an import or add an
> unfulfillable import somewhere in Nova or Glance. Could you post a diff for
> us to take a look at?
>
> Brian
>
>
>
> On Jun 25, 2012, at 7:03 AM, Leander Bessa Beernaert wrote:
>
> I've just added a new file and added a new method in the connection.py of
> libvirt. Those are the changes i made, surely they haven' screwed up the
> test system :/
>
> On Mon, Jun 25, 2012 at 3:00 PM, Joseph Suh  wrote:
>
>> Leander,
>>
>> If it works fine in master branch, the problem must be due to some
>> changes in your own branch.
>>
>> Thanks,
>>
>> Joseph
>>
>> 
>> (w) 703-248-6160
>> (c) 571-340-2434
>> (f) 703-812-3712
>> 3811 N. Fairfax Drive Suite 200
>> Arlington, VA, 22203, USA
>> http://www.east.isi.edu/~jsuh
>>
>> - Original Message -
>> From: "Leander Bessa Beernaert" 
>> To: "Joseph Suh" 
>> Cc: openstack@lists.launchpad.net
>> Sent: Monday, June 25, 2012 9:45:51 AM
>> Subject: Re: [Openstack] [OpenStack][Nova] No tests available in custom
>> branch
>>
>> I've tried all the options and the output is always, even with -V and -f:
>>
>>
>>
>>
>> --
>> Ran 0 tests in 0.000s
>> OK
>> Running PEP8 and HACKING compliance check...
>> 5 imports missing in this test environment
>>
>>
>> The tests run just fine on the master branch :/
>>
>>
>> On Mon, Jun 25, 2012 at 2:39 PM, Joseph Suh < j...@isi.edu > wrote:
>>
>>
>> Leander,
>>
>> Did you give -V -f option? If you post your log, it would be easier to
>> help.
>>
>> Thanks,
>>
>> Joseph
>>
>> 
>> (w) 703-248-6160
>> (c) 571-340-2434
>> (f) 703-812-3712
>> 3811 N. Fairfax Drive Suite 200
>> Arlington, VA, 22203, USA
>> http://www.east.isi.edu/~jsuh
>>
>>
>>
>> - Original Message -
>> From: "Leander Bessa Beernaert" < leande...@gmail.com >
>> To: openstack@lists.launchpad.net
>> Sent: Monday, June 25, 2012 9:13:43 AM
>> Subject: [Openstack] [OpenStack][Nova] No tests available in custom branch
>>
>>
>> Hello,
>>
>>
>> I've created a separate branch in Nova to test my code out. However,
>> every time i attempt to run the command "run_tests.sh" it says it has 0
>> tests to be run. I followed the guide from
>> http://wiki.openstack.org/GerritWorkflow to setup the branch. Did i miss
>> something?
>>
>>
>> Regards,
>> Leander
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] No tests available in custom branch

[Brian Waldon]

I usually run into this kind of problem when I break an import or add an 
unfulfillable import somewhere in Nova or Glance. Could you post a diff for us 
to take a look at?

Brian


On Jun 25, 2012, at 7:03 AM, Leander Bessa Beernaert wrote:

> I've just added a new file and added a new method in the connection.py of 
> libvirt. Those are the changes i made, surely they haven' screwed up the test 
> system :/
> 
> On Mon, Jun 25, 2012 at 3:00 PM, Joseph Suh  wrote:
> Leander,
> 
> If it works fine in master branch, the problem must be due to some changes in 
> your own branch.
> 
> Thanks,
> 
> Joseph
> 
> 
> (w) 703-248-6160
> (c) 571-340-2434
> (f) 703-812-3712
> 3811 N. Fairfax Drive Suite 200
> Arlington, VA, 22203, USA
> http://www.east.isi.edu/~jsuh
> 
> - Original Message -
> From: "Leander Bessa Beernaert" 
> To: "Joseph Suh" 
> Cc: openstack@lists.launchpad.net
> Sent: Monday, June 25, 2012 9:45:51 AM
> Subject: Re: [Openstack] [OpenStack][Nova] No tests available in custom branch
> 
> I've tried all the options and the output is always, even with -V and -f:
> 
> 
> 
> 
> --
> Ran 0 tests in 0.000s
> OK
> Running PEP8 and HACKING compliance check...
> 5 imports missing in this test environment
> 
> 
> The tests run just fine on the master branch :/
> 
> 
> On Mon, Jun 25, 2012 at 2:39 PM, Joseph Suh < j...@isi.edu > wrote:
> 
> 
> Leander,
> 
> Did you give -V -f option? If you post your log, it would be easier to help.
> 
> Thanks,
> 
> Joseph
> 
> 
> (w) 703-248-6160
> (c) 571-340-2434
> (f) 703-812-3712
> 3811 N. Fairfax Drive Suite 200
> Arlington, VA, 22203, USA
> http://www.east.isi.edu/~jsuh
> 
> 
> 
> - Original Message -
> From: "Leander Bessa Beernaert" < leande...@gmail.com >
> To: openstack@lists.launchpad.net
> Sent: Monday, June 25, 2012 9:13:43 AM
> Subject: [Openstack] [OpenStack][Nova] No tests available in custom branch
> 
> 
> Hello,
> 
> 
> I've created a separate branch in Nova to test my code out. However, every 
> time i attempt to run the command "run_tests.sh" it says it has 0 tests to be 
> run. I followed the guide from http://wiki.openstack.org/GerritWorkflow to 
> setup the branch. Did i miss something?
> 
> 
> Regards,
> Leander
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py

[Leander Bessa Beernaert]

I've implemented a diagnostics method for libvirt. The code works perfectly
with the devstack installation. However, when i run the test from
"run_tests.sh" this happens: http://paste.openstack.org/show/18754/. From
what i've been told from the irc channel, the data supplied by the test is
different than the one i'm currently receiving. Now, i'm unsure which data
type i should except from the get_diagnostics method.

On Mon, Jun 25, 2012 at 4:01 PM, Sean Dague wrote:

> On 06/25/2012 10:41 AM, Leander Bessa Beernaert wrote:
>
>> Hello,
>>
>> I'm working on the diagnostics method for libvirt. I've
>> successfully managed to test it while running it manually and with
>> devstack. However, the test case in test_virt_drivers.py fails since it
>> supplies a different data type to the method.
>>
>> Could it be possible that there's a certain mismatch between the two or
>> that this particular method accepts multiple sorts of data-types?
>>
>
> Can you be more specific with the issue? I've been in that code recently,
> so I might be able to help sort this out.
>
>-Sean
>
> --
> Sean Dague
> IBM Linux Technology Center
> email: sda...@linux.vnet.ibm.com
> alt-email: slda...@us.ibm.com
>
>
>
>
> __**_
> Mailing list: 
> https://launchpad.net/~**openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~**openstack
> More help   : 
> https://help.launchpad.net/**ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py

[Leander Bessa Beernaert]

I would like to add that I did not implement the test method, it was
already there. Also it supplies a different set of data than the one i
received when working with devstack.

Which of the data types should i assume to be correct, the one from
devstack or the one from the test?

On Mon, Jun 25, 2012 at 4:10 PM, Jay Pipes  wrote:

> You are not returning the data in the test method, whereas you are in the
> real method :)
>
> -jay
>
>
> On 06/25/2012 10:44 AM, Leander Bessa Beernaert wrote:
>
>> Sorry, forgot to add the code:
>>
>> *This is my method (this worked with devstack):*
>>
>> def get_diagnostics(self, instance):
>> dom = self._lookup_by_name(instance[**'name'])
>> return diagnostics.get_diagnostics(**dom)
>>
>>
>> *and this the test method*:
>>
>>
>>  def test_get_diagnostics(self):
>> instance_ref, network_info = self._get_running_instance()
>> self.connection.get_**diagnostics(instance_ref['**name'])
>>
>> On Mon, Jun 25, 2012 at 3:41 PM, Leander Bessa Beernaert
>> mailto:leande...@gmail.com>> wrote:
>>
>>Hello,
>>
>>I'm working on the diagnostics method for libvirt. I've
>>successfully managed to test it while running it manually and with
>>devstack. However, the test case in test_virt_drivers.py fails since
>>it supplies a different data type to the method.
>>
>>Could it be possible that there's a certain mismatch between the two
>>or that this particular method accepts multiple sorts of data-types?
>>
>>Regards,
>>Leander
>>
>>
>>
>>
>> __**_
>> Mailing list: 
>> https://launchpad.net/~**openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : 
>> https://launchpad.net/~**openstack
>> More help   : 
>> https://help.launchpad.net/**ListHelp
>>
>>
>
> __**_
> Mailing list: 
> https://launchpad.net/~**openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~**openstack
> More help   : 
> https://help.launchpad.net/**ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [infra] Stackforge issues: tests & mails

[James E. Blair]

Julien Danjou  writes:

> Looking for the check manually here:
>
>https://jenkins.stackforge.org/view/Ceilometer/job/gate-ceilometer-merge/
>
> seems to show that build #73 was related to this request but it has been
> successful. But it reviews and reports as "LOST".

Jenkins was missing the notification plugin which is necessary for use
with Zuul.  I also noticed that the Verified category had not been
expanded to -2,+2 as it had on OpenStack's jenkins.  I addressed both of
those problems, and uploaded a test change to see that things are
working:

  https://review.stackforge.org/#/c/234/

It looks like the two new jobs didn't run.  I believe that is because of
an unfortunate typo in the jenkins job filler YAML for those jobs: there
is an extra 'e' in ceilometer:

  https://jenkins.stackforge.org/job/gate-ceilometeer-python26-essex/?

-Jim

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py

[Sean Dague]

On 06/25/2012 10:41 AM, Leander Bessa Beernaert wrote:

Hello,

I'm working on the diagnostics method for libvirt. I've
successfully managed to test it while running it manually and with
devstack. However, the test case in test_virt_drivers.py fails since it
supplies a different data type to the method.

Could it be possible that there's a certain mismatch between the two or
that this particular method accepts multiple sorts of data-types?


Can you be more specific with the issue? I've been in that code 
recently, so I might be able to help sort this out.


-Sean

--
Sean Dague
IBM Linux Technology Center
email: sda...@linux.vnet.ibm.com
alt-email: slda...@us.ibm.com



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py

[Jay Pipes]

You are not returning the data in the test method, whereas you are in 
the real method :)


-jay

On 06/25/2012 10:44 AM, Leander Bessa Beernaert wrote:

Sorry, forgot to add the code:

*This is my method (this worked with devstack):*
 def get_diagnostics(self, instance):
 dom = self._lookup_by_name(instance['name'])
 return diagnostics.get_diagnostics(dom)


*and this the test method*:

  def test_get_diagnostics(self):
 instance_ref, network_info = self._get_running_instance()
 self.connection.get_diagnostics(instance_ref['name'])

On Mon, Jun 25, 2012 at 3:41 PM, Leander Bessa Beernaert
mailto:leande...@gmail.com>> wrote:

Hello,

I'm working on the diagnostics method for libvirt. I've
successfully managed to test it while running it manually and with
devstack. However, the test case in test_virt_drivers.py fails since
it supplies a different data type to the method.

Could it be possible that there's a certain mismatch between the two
or that this particular method accepts multiple sorts of data-types?

Regards,
Leander




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [metering] need commit approval on DB API

[Doug Hellmann]

During last week's meeting we approved the DB API put forward, at least as
a first pass until we implement a couple of the plugins to actually talk to
databases. I need approval on the change (
https://review.stackforge.org/#/c/227/) so I can use the API base class
while working on the first plugin this week.

Please take a few minutes to review the changes when you have time today.

Thanks,
Doug
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [metering] need review of instance metadata change

[Doug Hellmann]

After updating nova to emit more metadata about an instance when a
notification is sent, the next step was to update ceilometer to use that
information when converting the notification to a metering event. I have
that change up for review at https://review.stackforge.org/#/c/225/

I would like to get it checked in before starting work on the SQL engine
for the storage plugins in the collector. Please take a few minutes to give
it a review when you have time.

Thanks,
Doug
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py

[Leander Bessa Beernaert]

Sorry, forgot to add the code:

*This is my method (this worked with devstack):*
def get_diagnostics(self, instance):
dom = self._lookup_by_name(instance['name'])
return diagnostics.get_diagnostics(dom)


*and this the test method*:

 def test_get_diagnostics(self):
instance_ref, network_info = self._get_running_instance()
self.connection.get_diagnostics(instance_ref['name'])

On Mon, Jun 25, 2012 at 3:41 PM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:

> Hello,
>
> I'm working on the diagnostics method for libvirt. I've
> successfully managed to test it while running it manually and with
> devstack. However, the test case in test_virt_drivers.py fails since it
> supplies a different data type to the method.
>
> Could it be possible that there's a certain mismatch between the two or
> that this particular method accepts multiple sorts of data-types?
>
> Regards,
> Leander
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack][Nova] Possible inconsistency between devstack/nova execution and test_virt_drivers.py

[Leander Bessa Beernaert]

Hello,

I'm working on the diagnostics method for libvirt. I've
successfully managed to test it while running it manually and with
devstack. However, the test case in test_virt_drivers.py fails since it
supplies a different data type to the method.

Could it be possible that there's a certain mismatch between the two or
that this particular method accepts multiple sorts of data-types?

Regards,
Leander
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] No tests available in custom branch

[Leander Bessa Beernaert]

I've just added a new file and added a new method in the connection.py of
libvirt. Those are the changes i made, surely they haven' screwed up the
test system :/

On Mon, Jun 25, 2012 at 3:00 PM, Joseph Suh  wrote:

> Leander,
>
> If it works fine in master branch, the problem must be due to some changes
> in your own branch.
>
> Thanks,
>
> Joseph
>
> 
> (w) 703-248-6160
> (c) 571-340-2434
> (f) 703-812-3712
> 3811 N. Fairfax Drive Suite 200
> Arlington, VA, 22203, USA
> http://www.east.isi.edu/~jsuh
>
> - Original Message -
> From: "Leander Bessa Beernaert" 
> To: "Joseph Suh" 
> Cc: openstack@lists.launchpad.net
> Sent: Monday, June 25, 2012 9:45:51 AM
> Subject: Re: [Openstack] [OpenStack][Nova] No tests available in custom
> branch
>
> I've tried all the options and the output is always, even with -V and -f:
>
>
>
>
> --
> Ran 0 tests in 0.000s
> OK
> Running PEP8 and HACKING compliance check...
> 5 imports missing in this test environment
>
>
> The tests run just fine on the master branch :/
>
>
> On Mon, Jun 25, 2012 at 2:39 PM, Joseph Suh < j...@isi.edu > wrote:
>
>
> Leander,
>
> Did you give -V -f option? If you post your log, it would be easier to
> help.
>
> Thanks,
>
> Joseph
>
> 
> (w) 703-248-6160
> (c) 571-340-2434
> (f) 703-812-3712
> 3811 N. Fairfax Drive Suite 200
> Arlington, VA, 22203, USA
> http://www.east.isi.edu/~jsuh
>
>
>
> - Original Message -
> From: "Leander Bessa Beernaert" < leande...@gmail.com >
> To: openstack@lists.launchpad.net
> Sent: Monday, June 25, 2012 9:13:43 AM
> Subject: [Openstack] [OpenStack][Nova] No tests available in custom branch
>
>
> Hello,
>
>
> I've created a separate branch in Nova to test my code out. However, every
> time i attempt to run the command "run_tests.sh" it says it has 0 tests to
> be run. I followed the guide from http://wiki.openstack.org/GerritWorkflowto 
> setup the branch. Did i miss something?
>
>
> Regards,
> Leander
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] No tests available in custom branch

[Joseph Suh]

Leander,

If it works fine in master branch, the problem must be due to some changes in 
your own branch.

Thanks,

Joseph


(w) 703-248-6160
(c) 571-340-2434
(f) 703-812-3712
3811 N. Fairfax Drive Suite 200
Arlington, VA, 22203, USA
http://www.east.isi.edu/~jsuh

- Original Message -
From: "Leander Bessa Beernaert" 
To: "Joseph Suh" 
Cc: openstack@lists.launchpad.net
Sent: Monday, June 25, 2012 9:45:51 AM
Subject: Re: [Openstack] [OpenStack][Nova] No tests available in custom branch

I've tried all the options and the output is always, even with -V and -f: 




-- 
Ran 0 tests in 0.000s 
OK 
Running PEP8 and HACKING compliance check... 
5 imports missing in this test environment 


The tests run just fine on the master branch :/ 


On Mon, Jun 25, 2012 at 2:39 PM, Joseph Suh < j...@isi.edu > wrote: 


Leander, 

Did you give -V -f option? If you post your log, it would be easier to help. 

Thanks, 

Joseph 

 
(w) 703-248-6160 
(c) 571-340-2434 
(f) 703-812-3712 
3811 N. Fairfax Drive Suite 200 
Arlington, VA, 22203, USA 
http://www.east.isi.edu/~jsuh 



- Original Message - 
From: "Leander Bessa Beernaert" < leande...@gmail.com > 
To: openstack@lists.launchpad.net 
Sent: Monday, June 25, 2012 9:13:43 AM 
Subject: [Openstack] [OpenStack][Nova] No tests available in custom branch 


Hello, 


I've created a separate branch in Nova to test my code out. However, every time 
i attempt to run the command "run_tests.sh" it says it has 0 tests to be run. I 
followed the guide from http://wiki.openstack.org/GerritWorkflow to setup the 
branch. Did i miss something? 


Regards, 
Leander 
___ 
Mailing list: https://launchpad.net/~openstack 
Post to : openstack@lists.launchpad.net 
Unsubscribe : https://launchpad.net/~openstack 
More help : https://help.launchpad.net/ListHelp 


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] No tests available in custom branch

[Leander Bessa Beernaert]

I've tried all the options and the output is always, even with -V and -f:

--
> Ran 0 tests in 0.000s
> OK
> Running PEP8 and HACKING compliance check...
> 5 imports missing in this test environment


The tests run just fine on the master branch :/

On Mon, Jun 25, 2012 at 2:39 PM, Joseph Suh  wrote:

> Leander,
>
> Did you give -V -f option? If you post your log, it would be easier to
> help.
>
> Thanks,
>
> Joseph
>
> 
> (w) 703-248-6160
> (c) 571-340-2434
> (f) 703-812-3712
> 3811 N. Fairfax Drive Suite 200
> Arlington, VA, 22203, USA
> http://www.east.isi.edu/~jsuh
>
> - Original Message -
> From: "Leander Bessa Beernaert" 
> To: openstack@lists.launchpad.net
> Sent: Monday, June 25, 2012 9:13:43 AM
> Subject: [Openstack] [OpenStack][Nova] No tests available in custom branch
>
>
> Hello,
>
>
> I've created a separate branch in Nova to test my code out. However, every
> time i attempt to run the command "run_tests.sh" it says it has 0 tests to
> be run. I followed the guide from http://wiki.openstack.org/GerritWorkflowto 
> setup the branch. Did i miss something?
>
>
> Regards,
> Leander
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [OpenStack][Nova] No tests available in custom branch

[Joseph Suh]

Leander,

Did you give -V -f option? If you post your log, it would be easier to help.

Thanks,

Joseph


(w) 703-248-6160
(c) 571-340-2434
(f) 703-812-3712
3811 N. Fairfax Drive Suite 200
Arlington, VA, 22203, USA
http://www.east.isi.edu/~jsuh

- Original Message -
From: "Leander Bessa Beernaert" 
To: openstack@lists.launchpad.net
Sent: Monday, June 25, 2012 9:13:43 AM
Subject: [Openstack] [OpenStack][Nova] No tests available in custom branch


Hello, 


I've created a separate branch in Nova to test my code out. However, every time 
i attempt to run the command "run_tests.sh" it says it has 0 tests to be run. I 
followed the guide from http://wiki.openstack.org/GerritWorkflow to setup the 
branch. Did i miss something? 


Regards, 
Leander 
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [infra] Stackforge issues: tests & mails

[Julien Danjou]

On Mon, Jun 25 2012, Andrew Hutchings wrote:

> I can see the jobs on Jenkins just fine and puppet confirms there was no
> problem with deployment.  The Zuul service, however, was not running.
> This has been fixed.

Things changed indeed, but something is still wrong I think. I just sent
a review request:

 https://review.stackforge.org/#/c/232/

and Jenkins checked it. But we lost the link to Jenkins in the review.
Looking for the check manually here:

   https://jenkins.stackforge.org/view/Ceilometer/job/gate-ceilometer-merge/

seems to show that build #73 was related to this request but it has been
successful. But it reviews and reports as "LOST".

Any hint? :)

-- 
Julien Danjou
// eNovance  http://enovance.com
// ✉ julien.dan...@enovance.com  ☎ +33 1 49 70 99 81

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Openstack Dashboard Error

[Vaze, Mandar]

See  https://lists.launchpad.net/openstack/msg12548.html to get debug 
information on the webpage

-Mandar

From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net 
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On 
Behalf Of Trinath Somanchi
Sent: Monday, June 25, 2012 5:16 PM
To: Gabriel Hurley
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Openstack Dashboard Error

Hi-

I'm seeing this error, when I login to the Openstack Dashboard in the apache2 
error logs ..

[error] No handlers could be found for logger "openstack_dashboard"
In the Webpage its displaying  "
Internal Server Error

An unexpected error occurred while processing your request. Please try your 
request again.



"



Can any one help me out in resolving the issue...



Thanking you...

On Mon, Jun 25, 2012 at 10:48 AM, Gabriel Hurley 
mailto:gabriel.hur...@nebula.com>> wrote:
It sounds like your local_settings.py file is missing any logging 
configuration. The default config from the local_settings.py.example file is a 
good place to start.

If that’s not the case, then it would be helpful to know how you installed 
OpenStack/Horizon, what you’ve done to configure it, etc.

All the best,


-  Gabriel

From: 
openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
 
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net]
 On Behalf Of Trinath Somanchi
Sent: Sunday, June 24, 2012 10:03 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] Openstack Dashboard Error

Hi-

I'm seeing this error when I access the Openstack Dashboard through my browser.

[error] No handlers could be found for logger "openstack_dashboard".

Please help me resolve this issue.


--
Regards,
--
Trinath Somanchi,
+91 9866 235 130




--
Regards,
--
Trinath Somanchi,
+91 9866 235 130


__
Disclaimer:This email and any attachments are sent in strictest confidence for 
the sole use of the addressee and may contain legally privileged, confidential, 
and proprietary data.  If you are not the intended recipient, please advise the 
sender by replying promptly to this email and then delete and destroy this 
email and any attachments without any further use, copying or forwarding
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack][Swift] Global data backup, possible or not?

[Leander Bessa Beernaert]

Hello,

I've been tasked with finding out if Swift has any means of performing a
consistent global backup of all the information stored, which then could
easily be restored in case of failure.

I've been reading the documentation and these are my conclusions so far are:

- Swift maintains a copy of the data throughout each storage node;
- The data contained in these nodes, might or not be up to date. It depends
mainly on whether the replicator has propagated all the changes or not.


Is there a way in which i could backup the data from swift and ensure that
the backed-up data is up to date at the time of the backup?


Regards,
Leander
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Ops] OpenStack and Operations: Input from the Wild

[Endre Karlson]

Is it monitoring or metering ? Ceilometer does metering.

Endre.

2012/4/9 Huang Zhiteng 

> Thanks.  Now I understand the performance metrics you guys were talking
> about.  It'd be good if we can have some tool reporting numbers for a cloud
> just like 'mpstat', 'iostat' did for a system.
>
>
> On Mon, Apr 9, 2012 at 3:06 PM, Tim Bell  wrote:
>
>> Availability metrics for me are ones that allow me to tell if the service
>> is up, degraded or down. Each of us as we start production monitoring need
>> to work out how many nova, glance and swift processes of which type should
>> be running.  Furthermore, we need to add basic ‘ping’ style probes to see
>> that the services are responding as expected. 
>>
>> ** **
>>
>> Performance metrics are for cases where we want to record how well the
>> system is running. Examples of number of REST calls/second, VMs
>> created/second etc.  These are the kind of metrics which feed into capacity
>> planning, bottleneck identification, trending.
>>
>> ** **
>>
>> Building up an open, standard and consistent set will avoid duplicate
>> effort as sites deploy to production and allow us to keep the monitoring up
>> to date when the internals of OpenStack change.
>>
>> ** **
>>
>> Tim
>>
>> ** **
>>
>> *From:* Huang Zhiteng [mailto:winsto...@gmail.com]
>> *Sent:* 09 April 2012 05:42
>> *To:* Tim Bell
>> *Cc:* David Kranz; Andrew Clay Shafer;
>> openstack-operat...@lists.openstack.org; Duncan McGreggor; openstack
>>
>> *Subject:* Re: [Openstack] [Ops] OpenStack and Operations: Input from
>> the Wild
>>
>> ** **
>>
>> Hi Tim,
>>
>> Could you elaborate more on 'performance metrics'?  Like what kind of
>> metrics are considered as performance ones?  Thanks.
>>
>> On Sat, Apr 7, 2012 at 2:13 AM, Tim Bell  wrote:
>>
>>  
>>
>> Splitting monitoring into
>>
>>  
>>
>> 1.   Gathering of metrics (availability, performance) and reporting
>> in a standard fashion should be part of OpenStack. 
>>
>> 2.   Best practice sensors should sample the metrics and provide
>> alarms for issues which could cause service impacts. Posting of these
>> alarms to a monitoring system should be based on plug ins
>>
>> 3.   Reference implementations for standard monitoring systems such
>> as Nagios should be available that queries the data above and feeds it into
>> the package selected
>>
>>  
>>
>> Each site does not want to be involved in defining the best practice.
>> Equally, each monitoring system should not have to have an intimate
>> understanding of OpenStack to produce a red/green light.  The components
>> for 1 and 2 fall under the associated openstack component. Component 3 is
>> the monitoring solution provider.
>>
>>  
>>
>> Tim
>>
>>  
>>
>> *From:* openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:
>> openstack-bounces+tim.bell=cern...@lists.launchpad.net] *On Behalf Of *David
>> Kranz
>> *Sent:* 06 April 2012 16:44
>> *To:* Andrew Clay Shafer
>> *Cc:* openstack-operat...@lists.openstack.org; openstack; Duncan
>> McGreggor
>> *Subject:* Re: [Openstack] [Ops] OpenStack and Operations: Input from
>> the Wild
>>
>>  
>>
>> This is a really great list! With regard to cluster health and
>> monitoring, I did a bunch of stuff with Swift before turning to nova and
>> really appreciated the
>> way each swift service has a "healthcheck" call that can be used by a
>> monitoring system. While I don't think providing a production-ready
>> monitoring system should be part of core OpenStack, it is the core
>> architects who really know what needs to be checked to ensure that a system
>> is healthy. There are various sets of poking at ports, process lists and so
>> on that Crowbar, Zenoss, etc. set up but it would be a big improvement for
>> deployers if each openstack service provided healthcheck apis based on
>> expert knowledge of what is supposed to be happening inside. That would
>> also insulate deployers from changes in the code that might impact what it
>> means to be running properly. Looking forward to the discussion.
>>
>>  -David
>>
>>
>>
>> On 4/6/2012 1:06 AM, Andrew Clay Shafer wrote: 
>>
>> Interested in devops.
>>
>>  
>>
>> Off the top of my head.
>>
>>  
>>
>> live upgrades
>>
>> api queryable indications of cluster health
>>
>> api queryable cluster version and configuration info
>>
>> enabling monitoring as a first class concern in OpenStack (either as a
>> cross cutting concern, or as it's own project)
>>
>> a framework for gathering and sharing performance benchmarks with
>> architecture and configuration
>>
>>  
>>
>>  
>>
>> On Thu, Apr 5, 2012 at 1:52 PM, Duncan McGreggor 
>> wrote:
>>
>> For anyone interested in DevOps, Ops, cloud hosting management, etc.,
>> there's a proposed session we could use your feedback on for topics of
>> discussion:
>>  http://summit.openstack.org/sessions/view/57
>>
>> Respond with your thoughts and

Re: [Openstack] HVM + Xen Hypervisor via libvirt possible?

[Li Wang]

I will discuss with my team to decide which aproach we'll take, and reply
to this mail whenever there is something out.

Thanks all guys

Regards,
Wang Li


2012/6/22 John Garbutt 

> I have asked some of the Xen.org guys if they know anyone who has time to
> fix this.
> I will let you know if I have any luck.
>
> But yes, the XenAPI driver (talking to XCP) is probably the best way
> forward with Xen right now.
> If there are any blockers making that work, I am happy to help were I can.
>
> Cheers,
> John
>
> -Original Message-
> From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net[mailto:
> openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On
> Behalf Of Thomas Goirand
> Sent: 22 June 2012 2:40
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] HVM + Xen Hypervisor via libvirt possible?
>
> On 06/22/2012 05:56 PM, Daniel P. Berrange wrote:
> >> 3. or some good reasons to migrate from Xen to KVM?
> > I'd favour KVM for a variety of reasons, but lets not turn this into a
> > bikeshed discussion about which is best ;-P
>
> Let's put it this way: if you want to run with libvirt and Openstack, then
> yes, you should probably switch to KVM. But if you want to keep Xen, then
> you should probably switch to XCP.
>
> Thomas
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Openstack Dashboard Error

[Trinath Somanchi]

Hi-

I'm seeing this error, when I login to the Openstack Dashboard in the
apache2 error logs ..

[error] No handlers could be found for logger "openstack_dashboard"

In the Webpage its displaying  "
Internal Server Error

An unexpected error occurred while processing your request. Please try your
request again.


"


Can any one help me out in resolving the issue...


Thanking you...


On Mon, Jun 25, 2012 at 10:48 AM, Gabriel Hurley
wrote:

>  It sounds like your local_settings.py file is missing any logging
> configuration. The default config from the local_settings.py.example file
> is a good place to start.
>
> ** **
>
> If that’s not the case, then it would be helpful to know how you installed
> OpenStack/Horizon, what you’ve done to configure it, etc.
>
> ** **
>
> All the best,
>
> ** **
>
> **-  **Gabriel
>
> ** **
>
> *From:* 
> openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto:
> openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On
> Behalf Of *Trinath Somanchi
> *Sent:* Sunday, June 24, 2012 10:03 PM
> *To:* openstack@lists.launchpad.net
> *Subject:* [Openstack] Openstack Dashboard Error
>
> ** **
>
> Hi-
>
> I'm seeing this error when I access the Openstack Dashboard through my
> browser.
>
> [error] No handlers could be found for logger "openstack_dashboard".
>
> Please help me resolve this issue.
>
>
> --
> Regards,
> --
> Trinath Somanchi,
>
> +91 9866 235 130
>
> ** **
>



-- 
Regards,
--
Trinath Somanchi,
+91 9866 235 130
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [infra] Stackforge issues: tests & mails

[Julien Danjou]

On Mon, Jun 25 2012, Andrew Hutchings wrote:

> As we have pointed out several times the Stackforge Gerrit mail is
> unreliable.  This is because the Stackforge setup is hosted in HP Cloud
> and they have (quite rightly) anti-spam measures such as port 25 rate
> limiting.  We have a plan to resolve this soon but it is not an easy
> fix.  In the mean time the #stackforge-dev IRC channel can be used for
> Gerrit bot notifications.

Ok, I though it was solved actually. No problem then, we'll suffer in
silence until that can be really solved. :-)

> I can see the jobs on Jenkins just fine and puppet confirms there was no
> problem with deployment.  The Zuul service, however, was not running.
> This has been fixed.

Great, thank you Andrew! :)

-- 
Julien Danjou
// eNovance  http://enovance.com
// ✉ julien.dan...@enovance.com  ☎ +33 1 49 70 99 81

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Allow keystone users to know their rights

[Alexey Ababilov]

Hi!

Currently, user can obtain information about his rights (roles, tenants,
endpoints) only saving response to POST /tokens query. If you are a
non-privileged user, have a token, and haven't saved the mentioned
response, you cannot know your rights - you have to make another POST
/tokens query and retrieve a new token.

However, if you are a keystone admin, you can GET /tokens/{token_id} and
retrieve extended information for token of any user.

Is it a security measure? Would it be acceptable if an ordinary user were
allowed to get his token data in any moment? There could be a GET
/tokens/{token_id} call that returns data for valid token_id or signals
that it is invalid.

-- 
Alessio Ababilov
Software Engineer
Grid Dynamics
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [infra] Stackforge issues: tests & mails

[Andrew Hutchings]

Hi Julien,

On 25/06/12 10:15, Julien Danjou wrote:
> We've a couple of problem on Stackforge currently with at least the
> ceilometer project.
> 
> First, I don't receive any email from Gerrit anymore since several days.
> :-(

As we have pointed out several times the Stackforge Gerrit mail is
unreliable.  This is because the Stackforge setup is hosted in HP Cloud
and they have (quite rightly) anti-spam measures such as port 25 rate
limiting.  We have a plan to resolve this soon but it is not an easy
fix.  In the mean time the #stackforge-dev IRC channel can be used for
Gerrit bot notifications.

> Secondly, I've added a bunch of tests for Essex on Jenkins days ago, but
> it seems they are either not complete or not deployed. The changes are:
> 
>
> https://github.com/openstack/openstack-ci-puppet/commit/15e8d50de49dccb5958ec241638e7609d722d697
> 
> Could someone check this both issues?

I can see the jobs on Jenkins just fine and puppet confirms there was no
problem with deployment.  The Zuul service, however, was not running.
This has been fixed.

Kind Regards
-- 
Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [OpenStack][Nova] Snapshot stuck in Queued state, no erros found in compute log

[Leander Bessa Beernaert]

Hello,

I've performed snapshots over and over without ever running into trouble,
however now one of them is stuck in the Queued state. I've searched the
machine's compute.log for any indication of an error, but nothing showed
up. I did a quick search and usually the erros appear in the compute.log or
the libivirtd.log. The only thing i found in the libvirtd.log were these
two lines:

2012-06-25 10:37:05.957+: 6830: warning : qemuCapsInit:856 : Failed to
> get host power management capabilities
> 2012-06-25 10:37:06.612+: 6831: error : virExecWithHook:328 : Cannot
> find 'pm-is-supported' in path: No such file or director


Could that be the problem?

Regards,
Leander
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Hashing image files

[Alexey Ababilov]

Hi!

I am curious to know: is it necessary for nova to save images in file which
names are hashes from image IDs (UUIDs)?

Nova saves root image under its sha1 hash:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/connection.py#L1214
but it saves kernel and ramdisk under their original IDs:
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/connection.py#L1199
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/connection.py#L1206

Is it a security measures?


-- 
Alessio Ababilov
Software Engineer
Grid Dynamics
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] XCP with DevStack

[John Garbutt]

From: Thomas Goirand
> I wrote it before, and I will write it again: a shell script is not, and will 
> never
> replace, a documentation. What you need to do is write enough
> documentation so that an experienced admin can write his own script, not
> the other way around! So please write a decent tutorial.

I don' t disagree, it's by no means perfect at the moment.
I plan to write a tutorial at some point soon, to complement the scripts.

My docs plans for Folsom are:
- Update the getting started guide for new DevStack
- Review docs for KVM specific material
- Raise and fix bugs around the above issues
- Write a manual getting started guide

Hopefully that should leave us in a better position, and hopefully I will get 
on to that soon.
Afraid QA and coding currently proving higher priority.

Cheers,
John

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] XCP with DevStack

[John Garbutt]

Glad your networking is fine :)

One other possibility is, do you have anything in the PRESEED_URL variable?
Are you OK to share your localrc file?

Cheers,
John

From: r...@midokura.jp [mailto:r...@midokura.jp] On Behalf Of Ishimoto, Ryu
Sent: 25 June 2012 3:49
To: John Garbutt
Cc: Takaaki Suzuki; openstack@lists.launchpad.net
Subject: Re: [Openstack] XCP with DevStack

Hi John,


I think that error means you don't have anything set in HOST_IP (i.e. IP 
address of the XenServer) at the point in install_os_domU.sh:
https://github.com/openstack-dev/devstack/blob/master/tools/xen/install_os_domU.sh#L257

The HOST_IP should have been setup by this (or whatever is in your localrc 
file):
https://github.com/openstack-dev/devstack/blob/master/tools/xen/install_os_domU.sh#L168


Thanks for pointing these out.  While tracing out the problem, interestingly, I 
noticed that HOST_IP was indeed set properly inside the script(and so was 
PRESEED_URL).  Even so, for whatever reason during the DomU install, the IP got 
stripped out from the preseed URL:  
http:///devstackubuntupreseed.cfg.


Have you got the networking working correctly on your XenServer on Ubuntu?
Ifconfig should list xenbr0 having an appropriate IP address.


Yes, networking is working properly.  It is solely a DomU installation issue 
that we are having with devstack + XCP 1.3.  Everything else is working like a 
charm so far.

Good to know that you have already gotten it to work on 12.04.  It is most 
likely some silly configuration mistake that I've made that's causing this.  I 
will try digging a bit more myself and will let you know if I come across any 
interesting finding.

Thanks!
Ryu


Hope that helps,
John

From: r...@midokura.jp 
[mailto:r...@midokura.jp] On Behalf Of Ishimoto, Ryu
Sent: 22 June 2012 3:11
To: John Garbutt
Cc: Takaaki Suzuki; 
openstack@lists.launchpad.net
Subject: Re: [Openstack] XCP with DevStack

Hi John,

Thanks for all your help.  I have a question regarding your patch to make 
devstack work with XCP (https://review.openstack.org/#/c/7673/).  Does this 
patch apply to devstack with XCP 1.3.2(the package version that comes with 
Ubuntu 12.04?)  We verified that devstack does install without a problem with 
XCP 1.5 but we are still having issues with 1.3.2.

After looking into this issue a bit further, we noticed that the problem occurs 
during the OpenStack DomU VM installation process.  The preseed file location 
is incorrect ('http:///devstackubuntupressed.cfg') even though this file was  
copied to the correct location by the script prior to the installation step.  
Due to our lack of knowledge in this matter, all we could manage was to 
hard-code the proper URL in the kernel parameter set in  
'tools/xen/scripts/install-os-vpx.sh' script.  To be more precise, we added the 
hard-coded URL in the generation of kernel parameters in 'set_kernel_params()' 
method, and this successfully got us through the installation process.  
Although this temporary hack got us moving forward, we would love to get some 
inputs on how we can actually fix this.

We would really like devstack to work with 1.3, so if you or anyone could point 
us in the right direction, we would be more than happy to help out on this.

Thanks in advance!

Cheers,
Ryu

On Fri, Jun 1, 2012 at 9:18 PM, John Garbutt 
mailto:john.garb...@citrix.com>> wrote:
Hi,

I assume you are using xcp-xapi in Ubuntu. First of all, is it all running 
correctly (i.e. xe vm-list is returning correctly):
http://wiki.xen.org/wiki/Using_XCP_-_preparing_the_toolstack

It turns out the current DevStack will not work with this, but I have pushed 
some changes to support it:
https://review.openstack.org/#/c/7673/

The networking configuration can be a little confusing, there is an overview on 
the wiki:
http://wiki.openstack.org/XenServer/NetworkingFlags

The DevStack flags are there to configure each of the VIFs on the DomU, the 
defaults can be seen here:
https://github.com/openstack-dev/devstack/blob/master/tools/xen/xenrc

If things are still un clear, do ask some more questions.
I have plans to document this exact setup in some detail in the near future.
Feel free to add to these docs on the wiki.

Thanks,
John

> -Original Message-
> From: 
> openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net
> [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net]
> On Behalf Of Takaaki Suzuki
> Sent: 01 June 2012 10:12
> To: openstack@lists.launchpad.net
> Cc: dev
> Subject: [Openstack] XCP with DevStack
>
> Hi all.
>
> I need your knowledge. :)
> I prepared XCP plus OpenvSwitch with Ubuntu precise on own environment.
>
> And I want to prepare DevStack for XCP(Ubuntu).
> htt

[Openstack] [infra] Stackforge issues: tests & mails

[Julien Danjou]

Hi infra team,

We've a couple of problem on Stackforge currently with at least the
ceilometer project.

First, I don't receive any email from Gerrit anymore since several days.
:-(

Secondly, I've added a bunch of tests for Essex on Jenkins days ago, but
it seems they are either not complete or not deployed. The changes are:

   
https://github.com/openstack/openstack-ci-puppet/commit/15e8d50de49dccb5958ec241638e7609d722d697

Could someone check this both issues?

Thanks in advance!

Cheers,
-- 
Julien Danjou
// eNovance  http://enovance.com
// ✉ julien.dan...@enovance.com  ☎ +33 1 49 70 99 81

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Swift] Lost of an object data file is not detected

[山縣陽]

Hi mike,

Thank you for your answer.

I understand that swift can't detect missing object files.
And I am afraid of performance of object-auditor too.

Best regards,
   You Yamagata


2012/6/25 Michael Barton :
> On Sun, Jun 24, 2012 at 9:05 PM, 山縣陽  wrote:
>> But if I removed the data file, no process detected it  and the data
>> files was not recovered.
>> Is this a bug?  or is there any way to detect a data file lost case?
>
> Nope, there's nothing that'll detect missing data files once the
> system's in a steady state.
>
> Eventually, we'd like the auditor process that looks for corrupt files
> to also rebuild indexes as it goes, so we can catch those types of
> problems.  But that guy can take months to traverse a production
> storage node, so it'll probably always be a bad idea to just go and
> delete data files.
>
> - Mike

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [metering] Cinder usage data retrieval

[Nick Barcet]

On 06/21/2012 12:44 PM, Thomas, Duncan wrote:
> John Griffith on 20 June 2012 18:26 wrote:
> 
> 
>> On Wed, Jun 20, 2012 at 10:53 AM, Nick Barcet
>>  wrote:
>>> What we want is to retrieve the maximum amount of data, so we can
>> meter
>>> things, to bill them in the end. For now and for Cinder, this would
>>> first include (per user/tenant):
>>> - the amount of reserved volume space
>>> - the amount of used volume space
>>> - the number of volumes
>>> but we'll need probably more in a near future.
> 
> 
>> We should chat about how things are shaping up so far and how you're
>> implementing things on the other sides (consistency where
>> practical/possible).  Also, it sort of depends on the architecture and
>> use model details of Ceilometer, which I hate to admit but I'm not
>> really up to speed on.
>>
>> My first reaction/thought is the best most appropriate place to tie in
>> is via the python-cinderclient.  There would be a number of ways to
>> obtain some of this info, whether deriving it or maybe some extensions
>> to obtain things directly.
> 
> One thing to watch for here is access control... Don't want one tenant 
> able to find out about another's usage. Probably not important on a private
> cloud deployment, but certainly important in the public cloud space. Having
> a separate endpoint to do this kind of admin stuff over also means you can
> have much tighter IP level access controls...

It would seem to me that the easiest way would be for calls that are
emitted from the same host as cinder manager on the local interface to
be handled as "admin" calls. We could then place Ceilometer's cinder
agent on the same host, which would not be allowed to any user, thus not
creating a breach of security.

Thoughts?

Nick




signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp