Exactly. It would be really ugly to import something like xxx-yyy-zzz.
On Wed, Feb 22, 2012 at 3:24 PM, Alexey Eromenko wrote:
> On Wed, Feb 22, 2012 at 9:21 AM, Zhongyue Luo wrote:
> > Before we discuss whether the packages should be renamed or not, isn't it
> > unorthodox to have a hyphen in
On Wed, 2012-02-22 at 16:05 +0800, Zhongyue Luo wrote:
> Exactly. It would be really ugly to import something like xxx-yyy-zzz.
Alexey means the DEB package and not the name of the packaged stuff.
You can call python-whatever your package and the contents have the
hierarchy you want like whatever
I've uploaded the checks we use in production here at Spil Games to
https://github.com/spilgames/swift. Besides check_swift (which is a functional
test) everything's meant to gather statistics from the cluster and we're
looking to replace that with a Graphite-based solution to avoid having to pa
2012/2/22 Zhongyue Luo :
> Before we discuss whether the packages should be renamed or not, isn't it
> unorthodox to have a hyphen in a package name?
Out of the 38480 packages available on amd64 in Ubuntu Precise, 28910
have a hyphen in their package name.
--
Soren Hansen | http://li
I thought you meant the python package name, my bad.
On Wed, Feb 22, 2012 at 4:57 PM, Soren Hansen wrote:
> 2012/2/22 Zhongyue Luo :
> > Before we discuss whether the packages should be renamed or not, isn't it
> > unorthodox to have a hyphen in a package name?
>
> Out of the 38480 packages avai
Hi All,
I have just pushed a two line patch for
https://bugs.launchpad.net/quantum/+bug/938403
https://review.openstack.org/#change,4388
This patch is pushed to cloudbuilders/devstack.git but in another
thread, I just read that there's
one more devstack repo openstack-dev/devstack.git. On c
openstack-dev/devstack.git is the main repo.
The project summary for cloudbuilders/devstack.git states,
"THIS IS A MIRROR OF https://github.com/openstack-dev/devstack";
I guess someone has a dependency on cloudbuilders/devstack.git that
they can't give up just yet.
On 22 February 2012 09:45, De
Hi,
after successfull configuration of openstack object storage.. i tried to
test the installation
swauth-add-user -K swauthkey -A http://10.30.91.80:8080/swauth/ -a
system root testpass
error on /var/log/meesage
Feb 21 22:06:18 ostack-proxyserver proxy-server ERROR with Account server
10.30.91
openstack-dev/devstack.git is the main repo.
The project summary for cloudbuilders/devstack.git states,
"THIS IS A MIRROR OF https://github.com/openstack-dev/devstack";
I guess someone has a dependency on cloudbuilders/devstack.git that
they can't give up just yet.
On 22 February 2012 09:45, Dee
Could be a problem with the URL (/swauth rather than /auth). Try this,
swauth-add-user -K swauthkey -A http://10.30.91.80:8080/auth/ -a
system root testpass
On 22 February 2012 10:16, Sudhakar Maiya wrote:
> Hi,
>
> after successfull configuration of openstack object storage.. i tried to
> test
Hey guys,
I successfully installed a single-node with the stackops-distro. However I
encountered an error while uploading an image to nova using
"uec-publish-tarball" command.
Here is what I did:
//Execute command to upload
root@nova-controller:~# uec-publish-tarball
lucid-server-cloudimg
when i tried with below command
swauth-add-user -K swauthkey -A http://10.30.91.80:8080/auth/ -a system
root testpass
error
Account creation failed: 500 Server Error
User creation failed: 500 Server Error
Regards
Sudhakar
On Wed, Feb 22, 2012 at 4:07 PM, Adrian Smith wrote:
> Could be a prob
Is there anything of interest in your logs? This will either be
/var/log/syslog or /var/log/swift/?. Depends how you configured it in
/etc/swift/proxy-server.conf.
On 22 February 2012 13:47, Sudhakar Maiya wrote:
> when i tried with below command
>
> swauth-add-user -K swauthkey -A http://10.30.
Hello,
I'm trying to get started with Tempest and I would really like to be
able to see a running setup somewhere. I'm getting a lot of tests
failing and I don't know if it's because of my setup or because of bugs
in Tempest or incompatibilities with the current code in the other
components.
There is currently a bug https://bugs.launchpad.net/tempest/+bug/933845
that will prevent tempest from working with keystone. That ticket
provides a workaround but still not all of the tests are working at the
moment. I think the goal is for tempest to become actively run but we
are not there
On 02/21/2012 10:28 PM, Daryl Walleck wrote:
That time still works for me. Would be starting that this week (tomorrow)?
Yes, please :) And I heard from many other members that it would work,
too, and nobody said that the change would not work...
I've updated the wiki:
http://wiki.openstack.
We're running Tempest as part of our continuous build. For the bug you're
referring to David, there is a configuration in Tempest where the name of the
Nova/Compute project can be set, so I don't think its fair to say that Tempest
is currently broken. However, I am working on a more comprehensiv
Indeed, as soon as someone says "I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it..." we'll start running it in Jenkins. But so far I've heard from
the Tempest developers that it's not quite ready yet.
-Jim
David Kranz writes:
> There is
Hi all -
I moved the OpenStack calendar item for the QA meeting as well, let me
know if it looks accurate to you.
Thanks,
Anne
On Wed, Feb 22, 2012 at 9:35 AM, Jay Pipes wrote:
> On 02/21/2012 10:28 PM, Daryl Walleck wrote:
>>
>> That time still works for me. Would be starting that this week (t
To land Nexenta volume driver, we need review and approval on two changes:
- SnapshotIsBusy: https://review.openstack.org/1416
- driver itself: https://review.openstack.org/4204
I hope, there is some number of kind people who can give me some +1s or
comments on them.
Vish had already reviewed the
If John Dickinson can steal me a 30 minute block at the conference I'll
probably be giving a talk about it, but we (Rackspace) started switching to
Graphite back in December. We're basically just following the etsy cookbook to
"graph all the things!".
We're using https://github.com/pandemicsy
Yuriy,
Nova is currently in the essex-4 part of the development cycle which includes a
Feature Freeze. No branches containing features should be merged in until the
next part of the cycle. You can submit a feature freeze exception request or
wait for the Folsom branch to be active (early March?
I have proposed a DevStack branch that supports Fedora 16 at
https://review.openstack.org/4364.
Not everything is working yet, as outlined below. I am proposing now
anyway to get feedback on the direction and some of the decisions I
made along the way. Even though this release is targeted specifi
Hi all,
Currently I'm trying to track how a refresh of the security groups is handled
(upon creation or deletion of a vm). Following through the code I get to
'do_refresh_security_group_rules' in libvirt/firewall.py. Up to this point the
security group in question has been carried through howev
There is already FFe for this, and this changes are in Gerrit for some time
already.
Yesterday there was an approval to give us some time to land this on
Community Meeting.
So everybody is ready to accept this change, but it looks like it's hard to
get things reviewed this days.
Kind regards, Yuri
On 02/22/2012 11:45 AM, Florian Hines wrote:
If John Dickinson can steal me a 30 minute block at the conference I'll
probably be giving a talk about it, but we (Rackspace) started switching
to Graphite back in December. We're basically just following the etsy
cookbook to "graph all the things!".
On 02/22/2012 10:49 AM, James E. Blair wrote:
Indeed, as soon as someone says "I have Tempest working on a system
configured by devstack with a repeatable process, here's how I did
it..." we'll start running it in Jenkins. But so far I've heard from
the Tempest developers that it's not quite rea
This is great news Dean, thank you!
I'll try using your patch to get tempest running on F16,
and I'll get back to you with any issues I encounter.
Cheers,
Eoghan
- Original Message -
> From: "Dean Troyer"
> To: openstack@lists.launchpad.net
> Sent: Wednesday, 22 February, 2012 5:04:03
On Wed, 2012-02-22 at 11:04 -0600, Dean Troyer wrote:
> I have proposed a DevStack branch that supports Fedora 16 at
> https://review.openstack.org/4364.
>
> Not everything is working yet, as outlined below. I am proposing now
> anyway to get feedback on the direction and some of the decisions I
>
Maybe soren has a comment on this, but as far as I can tell it looks like a
bug. It seems getting a list of instances that are in that group and
refreshing those would be the right approach.
Vish
On Feb 22, 2012, at 9:13 AM, McNally, Dave (HP Cloud Services) wrote:
> Hi all,
>
> Currently I
Looks like swift with keystone is working
swift -A http://192.168.122.14:5000/v2.0 -U adminTenant:adminUser -K
secretword -V 2.0 stat -v
StorageURL: https://192.168.122.14:8080/v1/AUTH_2
Auth Token: 999888777666
Account: AUTH_2
Containers: 0
Objects: 0
Bytes: 0
Accept-Ranges: bytes
-
To create a container with "st" tool:
http://docs.openstack.org/bexar/openstack-object-storage/admin/content/ch04s10.html
curl command would be something like:
curl -i -X PUT -H 'x-auth-token: '
'http://127.0.0.1:8080/v1//'
Hope that helps
Jo
From: Paras p
On 02/22/2012 05:04 PM, Dean Troyer wrote:
> I have proposed a DevStack branch that supports Fedora 16 at
> https://review.openstack.org/4364.
Thanks!
> tgtd is misbehaving on fedora16 for me: volumes don't work
That used to work but recently I noticed systemd hangup issues.
Does starting it lik
Essex-4 is almost here, and once it comes out, you’d probably want to
install it.
A bunch of folks from across the country and across Dell, Rackspace,
OpsCode, Niciria, Nokia and more, will be getting together on an
IRC/Skype (and in person) to hash out deployment issues to get the
major componen
Right now I'd mostly like to know what the reasoning was behind making
the driver only pick the first available local datastore, rather than
making it configurable? Also, on
http://nova.openstack.org/vmwareapi_readme.html it mentions
nova.network.vmwareapi_net for vlan networking support, but it d
Hello folks,
We’ve postponed the deadline for OpenStack Conference call for speakers.
We'd like your help to build out an informative and compelling agenda,
including user stories, technical advancements, best practices and
visions on the future of OpenStack.
The new deadline is February 29, 2012
To make database downgrade works in nova, we need review and approval on
the following change:
https://review.openstack.org/3891
I hope, there is some number of kind people who can give me some +1s or
comments on them.
The rational behind this patch is:
1.Make data(metadat, table and column def
I've successfully installed all OpenStack components with Keystone
authorization (well, mostly at least), but am now seeing an interesting problem
for new accounts (created in Dashboard).
Using my admin account, I issue a swift stat command and get the expected
response back from swift-proxy:
please check and let me know what needs to be done
On Wed, Feb 22, 2012 at 7:31 PM, Adrian Smith wrote:
> Is there anything of interest in your logs? This will either be
> /var/log/syslog or /var/log/swift/?. Depends how you configured it in
> /etc/swift/proxy-server.conf.
>
> On 22 February 2012
Hi Robert,
I had forogt that I intended to send out a reminder this afternoon. I
had intended to continue with the standard process of using
#openstack-meeting. The standing volume team meeting is still posted
on the meetings wiki page:
http://wiki.openstack.org/Meetings
There was a link to
Hey Anthony,
On Wed, Feb 22, 2012 at 3:11 AM, Anthony Young
wrote:
> Hey Tomoe,
>
>>
>> Great idea! Both of those sound good to me. Would you like to implement
>> this?:)
>
>
> Lol, perhaps, but at the very least this warrants a blueprint:
> https://blueprints.launchpad.net/nova/+spec/nova-creat
Just another reminder for folks in addition to the one Robert sent out
earlier this evening. Along with the proposed agenda in the original
email I sent out, I've also updated the meetings wiki page with
current information.
http://wiki.openstack.org/NovaVolumeMeetings
Look forward to catching up
42 matches
Mail list logo
