Now with pull requests
On Thu, Sep 6, 2012 at 11:49 AM, Sean Dague wrote:
> Looks like thanks to bcwaldon you wont have to wait much.
>
> Also, +1 for Vish.
>
>
> On 09/06/2012 02:12 PM, Duncan McGreggor wrote:
>>
>> /me waits for http://vishfacts.com/ ...
>>
>> On Thu, Sep 6, 2012 at 10:54 AM, M
With *all* services, if you know the endpoint you can query them
directly with the auth mechanism (either token or ec2 access/secret).
OpenStack has an identity service (keystone) that returns a catalog of
services (for discovery)
You don't need to look at the catalog if you know the endpoints.
Agree that there are pros and cons to caching at different layers.
As for plugins, in most places where we support memcache we revert to
an in-memory cache if it isn't configured.
The work that was done during essex was to make the metadata service
use either an external cache or internal cache.
There is the concept of "limits" that are very similar. Should we
align quotas & limits?
j
On Fri, Mar 16, 2012 at 2:56 PM, Kevin L. Mitchell
wrote:
> I wanted to let everyone know about a quota classes blueprint I've
> submitted; you can find the details here:
>
> * https://blueprints.launchpa
Maybe it is just me, but most reviews seem to take hours to days to
complete. I'm been sitting here waiting for a one line change to get
a second "+2 / approved" so I can redeploy our test cluster for the
last 2 hours.
When lots of people are active, reviews can be approved in quickly -
especiall
It would be neat to see one with all the projects together - in HD.
Since many contributors work on all the projects, we would see people
zooming all around the screen.
Is this possible?
On Mon, Mar 5, 2012 at 3:03 AM, Armaan wrote:
>
>
> Thanks everyone, i am delighted that you liked them.
>
That looks like a line from devstack.
I just did a fresh install of oneiric and ran devstack (kvm) and
didn't see this issue.
Any details?
Jesse
On Sun, Mar 4, 2012 at 11:12 PM, Shang Wu wrote:
> What is the environment that you used to deploy this? Did you specify the
> connection_type in the
Those should probably go into tempest.
The goal for exercises is that they are simple tests of the CLI that
users can read to see how to use the cloud.
Jesse
On Sat, Feb 25, 2012 at 7:22 AM, Chmouel Boudjnah wrote:
> Hi,
>
> I'd like to add a excercises to test swift3+s3token in devstack and
>
I'd love to hear more specifics about what needs more focus. These
issues are large and have been the major focus of the core team for a
while.
> * Nova is too big.
> Very few (if any) core developers are comfortable reviewing every
> part of the code base. In itself, this isn't necessarily
There are certainly folks who review changes to stable/diablo
So if you want to propose patches to the branch, please do!
On Tue, Feb 21, 2012 at 12:35 PM, Yun Mao wrote:
> Hi Anthony, the issues with stable/diablo branch are: mostly the left
> over VMs are not scrubbed cleanly, and EXTRA_FLAGS
There isn't yet an API for PCI/USB passthrough.
If your goals can be accomplished by tweaking the libvirt.xml template
(and no additional data), then you might be able to accomplish this
without any changes to nova.
If you need fine-grained control of passthrough parameters per VM,
then changes t
Yes
Light was the codename when it was an internal tool.
The first version was a couple hundred lines and supported all core APIs.
After it was decided it would be more effective to flesh out light than
continue to tweak the existing code base, it became the redux branch of the
official keystone
ugs.launchpad.net/keystone/+bugs?field.tag=redux We marked bugs
that are needed to land before this merge as CRITICAL, and before E4 as
HIGH.
>>>
>>> Post Merge:
>>>
>>> After merge we will continue im
Deliberate change.
It used to be that KVM and XS did different things as far as disk partitioning.
https://blueprints.launchpad.net/nova/+spec/disk-configuration-parity
Now a flavor can specify the root vs ephemeral partition size
independently instead of being decided by choice of hypervisor.
You can add a selection of images to your localrc and it will add them
automatically
https://github.com/cloudbuilders/devstack/blob/master/stackrc#L57
example localrc:
IMAGE_URLS=http://smoser.brickies.net/ubuntu/ttylinux-uec/ttylinux-uec-amd64-11.2_2.6.35-15_1.tar.gz,http://uec-images.ubuntu.co
the reason for adding tmux is that we were running into issues with
services not launching inside screen (due to a timing issue).
I'm for removing tmux - since the sleep between creating a screen &
using it has resolved the issue.
Jesse
On Wed, Feb 8, 2012 at 9:39 AM, Jay Pipes wrote:
> On 02/0
Silly thought: what about launching automating VM to do the work of
downloading and uploading the image to glance?
On Tue, Feb 7, 2012 at 4:21 PM, Tres Henry wrote:
> I think this is a slightly different (but related) use case. In this case the
> user wants to add an image to the configured Glan
At the end of devstack run it says:
echo "keystone is serving at
$KEYSTONE_SERVICE_PROTOCOL://$KEYSTONE_SERVICE_HOST:$KEYSTONE_SERVICE_PORT/v2.0/"
echo "examples on using novaclient command line is in exercise.sh"
echo "the default users are: admin and demo"
echo "the password: $ADM
I know that the RCB deploy team works with the Crowbar team on chef
recipes for that project.
Regarding the github.com/ansolabs & github.com/rcb recipes - I'll have
to delegate to Vishy who worked on those.
Jesse
On Mon, Feb 6, 2012 at 6:07 PM, Jay Pipes wrote:
> Hi Stackers,
>
> tl;dr
> -
Agreed. Supporting more than just ubuntu is important!
On Mon, Feb 6, 2012 at 5:22 PM, Joshua Harlow wrote:
> + There needs to be a way to install on multiple distributions (without
> saying go figure out the deps yourself).
>
> I know everyone is ubuntu, ubuntu, ubuntu, but this really needs to
>
> On 02/06/2012 10:37 AM, Jesse Andrews wrote:
>> I think having a session on devstack at the summit would be valuable.
>
> ++
>
>> I'm still torn on it being python vs. bash because I see
>> non-developers using it all the time because they can take snippets
I think having a session on devstack at the summit would be valuable.
I'm still torn on it being python vs. bash because I see
non-developers using it all the time because they can take snippets of
the shell script and use it.
Jesse
On Mon, Feb 6, 2012 at 10:29 AM, Joshua Harlow wrote:
> Hi all
ut LBaaS and the definition of OpenStack.
Jesse Andrews
Rackspace Cloud Builders
[1] the analogy I use is that the Apache Web Server doesn't try to be
Django or Rails, but instead be a great web server to run rails on top
of.
[2] in addition to the question about if lbaas belongs in core, the
inc
ion by dashboard
CLI Auth Blueprint: http://wiki.openstack.org/CLIAuth
Horizon openrc generation: http://dl.dropbox.com/u/891851/horizon-openrc.png
---
If any other teams have big plans for E4, it would be great to hear them.
Thanks!
Jesse Andrews on behalf of the entire Rackspace Cloud Builders team
_
There have been conversations about changing that. That nova should
use /etc/nova/nova.conf
Thoughts?
On Tue, Jan 24, 2012 at 10:40 AM, Jorge Luiz Correa wrote:
> When using Devstack the files are written to /opt/stack/. So, you
> can find nova.conf in /opt/stack/nova/bin/.
>
> Regards.
>
>
> O
VNC consoles used to be an openstackx extension. Anthony is working today
on moving it into openstack contrib.
On Wed, Jan 18, 2012 at 3:06 PM, Mohammad Banikazemi wrote:
> Thanks for the script.
> Maybe I am being paranoid or I have messed up my setup but since yesterday
> I cannot use VNC con
devstack-pi (play on version numbers and python)
On Wed, Jan 18, 2012 at 11:22 AM, Joshua Harlow wrote:
> Sure, this was just a name I picked. It can be renamed to anything, works
> for me. I just needed a name for a github project (and it seemed to make
> sense at the time, haha).
>
> -Josh
>
>
looks like you have instances running.
virsh list
then terminate the instances.
On Wed, Jan 18, 2012 at 8:15 AM, Debo Dutta (dedutta) wrote:
> Gabriel
>
>
>
> As a control experiment I ran devstack on a fresh vm using non Quantum
>
>
>
> Observations:
>
> · When I try to add a rule
I think a goal would be to have easy fabric integration.
Right now our fabric scripts for devstack look like:
@task
@parallel
def stop():
"""Kill devstack and all VMs running"""
run("killall -9 screen || true")
run("screen -wipe || true")
# note we can probably remove this once d
This is a known issue with master due to a change to how extension work
with nova. I expect it will be fixed within a day.
On Jan 17, 2012 12:08 AM, "Gary Kotton" wrote:
> Hi,
>
> When I connect to the dashboard after a devstack installation I get the
> following error:
>
> *Unable to get
Nice!
Jay - are you expecting folks to run this on the same server or in the
same rack as the glance server? (eg, do you expect the transfer
between the client and glance to make an noticeable impact on
performance)
Perhaps if people are going to share these numbers they should share
benchmarks
Agreed - filing a bug.
Jesse
On Sat, Dec 31, 2011 at 8:15 PM, Ewan Mellor wrote:
> We now have a script called ‘keystone’ as the entry point to
> python-keystoneclient, and a script called ‘keystone’ that launches a
> combined admin and service API server. Either could be /usr/bin/keystone.
> I
Devstack isn't for production. I recommend using packages (even if
they are your own).
repeat: WHAT FOLLOWS IS NOT FOR PRODUCTION!
If you are just experimenting with a multi-node dev deploy - you can
set a few options in your nova.conf:
--sql_connection=mysql://$MYSQL_USER:$PASS@$MASTER_IP/nova
Looks like you are missing the %tenant_id% in the service endpoint catalog
$BIN_DIR/keystone-manage $* endpointTemplates add RegionOne nova
http://%HOST_IP%:8774/v1.1/%tenant_id%
http://%HOST_IP%:8774/v1.1/%tenant_id%
http://%HOST_IP%:8774/v1.1/%tenant_id% 1 1
On Wed, Dec 21, 2011 at 11:10 PM, d
python-keystoneclient is based on python-novaclient, and is already in
use by horizon as mentioned.
What are the reasons for not using python-keystoneclient?
Jesse
On Fri, Dec 16, 2011 at 1:47 PM, Monty Taylor wrote:
> Hrm. For some reason I thought we'd already decided to use the
> 4P/python-k
IMPORTANT: this is NOT about removing EC2 api or admin apis - it is
about moving admin extensions to openstack api extensions.
When we first created nova, we created a set of admin apis that helped
make the project configurable without nova-manage. We shoved them
into the ec2 api layer since the
When you run devstack it should ask for your admin_password.
If you forgot what you set it will be recorded in the localrc file.
To access your cloud there are two users: admin and demo (with admin
privileges vs regular user) - both with the ADMIN_PASSWORD you set in
the localrc file.
On Thu, D
On Thu, Dec 15, 2011 at 8:43 AM, Scott Moser wrote:
> I'm just curious, what are the motivations behind inventing something
> other than the EC2 Metadata service? It is generally functional, and
> quite a lot can (and has) built atop this simple service.
I should clarify - the idea is that ec2 m
Definitely we should be filing bugs.
Jesse
On Thu, Dec 15, 2011 at 8:00 AM, Julien Danjou
wrote:
> On Thu, Dec 15 2011, Narayan Desai wrote:
>
>> Hello all. We've recently upgraded our cactus system to more recent
>> code. In the process of doing this, we've started logging whenever we
>> get tr
Great question.
Right now there are 3 approaches to metadata/runtime config:
* ec2 metadata service - http://169.254.169.254/ (used by ubuntu's
cloud-init for example)
* config drive - added in diablo
* xenstore via openstack agent - https://launchpad.net/openstack-guest-agents
* injecting fi
I agree except I though the preference was for
> instance_uuid = instance['uuid']
not
> instance_uuid = instance.uuid
(use dict's and don't assume sqlalchemy)
On Wed, Dec 14, 2011 at 11:19 PM, Devin Carlen wrote:
> Yes, we should absolutely push to make this more consistent across the board.
I would interpret that to include the snapshots - but I'm not sure
that is what I'd expect as a user.
On Wed, Dec 7, 2011 at 5:05 PM, Nachi Ueno
wrote:
> Hi folks
>
> I wanna make Delete server spec clear.
>
> The API doc says,
> "When a server is deleted, all images created from that server are
A tenant is what used to be called a project in nova, and an account in swift.
When you validate a token using keystone you get the "account"
(tenant) and the user who is performing the account (who is a member
of the tenant)
Jesse
On Sun, Nov 20, 2011 at 7:58 AM, John Dickinson wrote:
> I don'
What version of libvirt bin/d/python are you running?
on debian/ubuntu do:
dpkg -l | grep libvirt
On Thu, Oct 27, 2011 at 8:49 AM, Vishvananda Ishaya
wrote:
> I haven't seen this happen. Sounds like it may be a libvirt bug.
> On Oct 27, 2011, at 7:48 AM, mao weijie wrote:
>
> I have found n
I don't think the debate is whether to do migrations or not. I think
the debate should be:
Is there more value in not doing it the same way another openstack
project does it?
If you can use nova's method, then we get closer to having standard
operating procedures for openstack projects...
On
I'm not an expert ... adding some comments
On Tue, Oct 25, 2011 at 12:05 PM, Joseph Heck wrote:
> I've just dropped in place a bunch of developer documentation (RST) for
> Keystone - one in, one pending (https://review.openstack.org/#change,1089).
> Making these docs brought up a number of quest
++
On Tue, Oct 11, 2011 at 2:46 PM, Josh Kearney wrote:
> ++
>
> On Tue, Oct 11, 2011 at 3:59 PM, Brian Waldon
> wrote:
>>
>> I would like to propose we remove our implementation of OSAPI v1.0 from
>> Nova for the following reasons:
>>
>> 1) Our implementation is incomplete, and there are no (vi
Actually right now it doesn't re-check out.
You have to manually "pull" in the project you want to update.
I've got a patch that I want to get reviewed / fixed before I merge
https://github.com/cloudbuilders/devstack/pull/52 that will update the
repos on each run.
Jesse
2011/10/10 Joseph Heck :
If the request isn't coming into the nova-api then I recommend
checking the network path using tcpdump (or wireshark - there is a
curses version).
As you can see it tries 100 times to hit the metadata server so you
should see traffic every couple seconds
On Sat, Oct 1, 2011 at 1:59 PM, Shashank
There have been various discussions about this before.
There are actually two issues if you don't like a security breach on a
single node to compromise other systems:
* messages are not verifed
* database access is global
As you've said anyone with access to the queue can send any message
and ma
I know Sandy Walsh did novaclient and Devin Carlen did (the
deprecated) adminclient for nova.
They might be able to pitch in and help (irc?)
On Wed, Sep 28, 2011 at 8:26 AM, Jay Pipes wrote:
> We should be able to do that, yes. I have to figure out how to do it,
> but I will create a bug for it
, the normal flow?)
Jesse
On Wed, Sep 28, 2011 at 9:36 AM, Jay Pipes wrote:
> Am I to assume the below is going to be the Diablo+ release/package or
> whatever was agreed upon at the last #openstack-meeting?
>
> :)
>
> -jay
>
> 2011/9/28 Jesse Andrews :
>> at various p
at various points in time they have worked together. We
(cloudbuilders) keep a list of repositories that work well together.
# compute service
NOVA_REPO=https://github.com/openstack/nova.git
NOVA_BRANCH=2011.3
# image catalog service
GLANCE_REPO=https://github.com/cloudbuilders/glance.git
GLANCE
I can add "ami" style images to diablo nova/glance via:
wget
http://uec-images.ubuntu.com/natty/current/natty-server-cloudimg-amd64.tar.gz
tar -zxvf natty-server-cloudimg-amd64.tar.gz
glance add -A KEYSTONE_TOKEN name="uec-natty-kernel" is_public=true
container_format=aki \
Is there / will there be a git tag/branch for diablo in the
github.com/openstack/nova repository?
Thanks,
Jesse
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
If you aren't using qauntum you can get dashboard doing something like:
export DASH_DIR=path_to_dashboard_checkout
mkdir -p $DASH_DIR/openstack-dashboard/quantum
touch $DASH_DIR /openstack-dashboard/quantum/__init__.py
touch $DASH_DIR /openstack-dashboard/quantum/client.py
Then up
Can you guys create a readme or delete the file?
On Thu, Sep 8, 2011 at 4:00 PM, Monty Taylor wrote:
>
>
> On 09/08/2011 03:15 PM, Rick Harris wrote:
>> Just a quick announcement so no one is caught by surprise:
>>
>> Once
>> https://code.launchpad.net/~rconradharris/nova/backup_schedule_extensi
Devin,
Thank you for putting this so eloquently. I cannot agree more
+1000
On Aug 26, 2011 11:38 AM, "Devin Carlen" wrote:
> Hey all,
>
> I've been following the code vs architect debate that's been unfolding
over the past week or so. Here are some of the problems I've seen from my
point of view
I disagree. I find lots of valuable in github even if trunk merges require
gerrit.
Teams can (and IMHO should) use pull requests to improve the quality before it
is proposed to trunk. Pull requests to branches can be made while the work is
still in progress (sending patches to others branches
I highly advise running using mod_wsgi, gunicorn or other techniques that allow
you to run multiple application servers since the API calls dashboard makes to
nova/keystone/... are synchronous.
Jesse
On Aug 4, 2011, at 2:02 PM, Joshua Harlow wrote:
> Thanks that seemed to work.
>
> I think t
We need to make it more clear the relationship between keystone and
user/tenants.
When you authenticate against keystone, a service is sent a token with an
associated User/Tenant.
The current backend of keystone supports a specific tenant/user model, but as
far as the rest of openstack (nova
Todd was doing some work on keystone
https://github.com/rackspace/keystone/commit/722fcd8ebef3fe1268ace5c05e014f6a945abfab
It still needs some work and might not be at the right place.
Jesse
On Jun 21, 2011, at 4:31 PM, Tres Henry wrote:
> Trying to get a Swift+Keystone dev environment setu
A few of us were looking at starting to implement
http://wiki.openstack.org/SystemUsageData, starting with updating the
spec to reflect plans related to unified auth (the keystone project).
In the blueprint, it was called out that data was to be aggregated by
Account ID - which it claimed is NOT t
Sounds reasonable.
-- Sent from my Tandy 1000sx
Jesse Andrews
anotherje...@gmail.com
On May 4, 2011, at 11:19 AM, Ant Messerli wrote:
> So it sounds like the better path would be to just keep two channels for
> now, see how that goes, and then maybe revisit splitting out by project i
Atlas is an api/service which controls load balancers. Currently they
support zeus, but they have a model where folks can add additional software
like haproxy/pound/... much like nova supports additional
hypervisors/storage systems via "drivers"
On Apr 23, 2011 7:26 AM, "Thomas Goirand" wrote:
> O
The PBB talked a few meetings ago about the incubation process.
Incubation is a phase of saying "I want to align myself with openstack". Any
project can incubate, but to become core requires the PBB consent.
Competing projects (for db, lb, dashboards, ...) are welcome. Once the
project has prope
Agreed that auth needs improved. Multiple auths per site would be horrible.
Ziad just sent an email about the first phase and we (openstack community
members who care about auth) will work with ptls to make sure it works for
them.
On Apr 19, 2011 11:53 AM, "Ken Pepple" wrote:
> On Apr 19, 2011,
I like the simple solution (#3) as well.
It gets parity for the APIs while leaving more advanced topics for the NaaS
discussions.
-- Sent from my Tandy 1000sx
Jesse Andrews
anotherje...@gmail.com
On Apr 18, 2011, at 11:36 AM, Trey Morris wrote:
> Appears my response got lost somehow
+1
We were hoping to move it to an openstack admin api. Hopefully now that
openstack api 1.1 exists we can get traction on flushing it out with commands
like these (and those contained within the ec2 extensions for administration)
-- Sent from my Tandy 1000sx
Jesse Andrews
anotherje
hitectures) ! - I see someone else mentioned this, I just wanted to voice
support :)
-- Sent from my Tandy 1000sx
Jesse Andrews
anotherje...@gmail.com
On Apr 12, 2011, at 11:11 AM, Jay Pipes wrote:
> Hey all,
>
> We're in the planning stages for Diablo now, working on putting
>
The decision hasn't been made. The decision is to talk about it at the summit
and on the mailing list.
-- Sent from my Tandy 1000sx
Jesse Andrews
anotherje...@gmail.com
On Apr 8, 2011, at 3:08 PM, Rick Clark wrote:
>>
>> Therefore, at this time, we are only proposin
What to do when an instance dies is application specific.
Some applications may not care, autoscaling back to the proper size by
themselves. Other applications may need the resources to be returned in the
most recent state.
Currently openstack requires the user to handle recovery.
I expect there
I agree that things should be pluggable, but OpenStack needs to have a default.
Users need to know that they can point OpenStack client applications at
OpenStack providers and it should work.
I would prefer a signature based approach as the default (as signatures limits
replay attacks; token
ple.com
> image=api.example.com
> network=api.example.com
>
> Maybe this is something the auth services return?
>
>
> From: Jesse Andrews
> Date: Mon, 28 Feb 2011 19:53:01 -0800
> To: Erik Carlin
> Cc: "openstack@lists.launchpad.net"
> Subject: Re: [Open
I'm also confused because nova (compute/block/network) is in 1 repository
doesn't mean it isn't 3 different services.
We've talked about moving the services inside nova to not reaching inside of
each other via RPC calls and instead making HTTP calls. But they are mostly
already designed in a w
That's the goal.
The linked server is our playground. Still working through concurrency
issues.
On Feb 25, 2011 12:22 PM, "Jay Pipes" wrote:
> I'm assuming we're adding this to the openstack.org Hudson setup?
>
> -jay
>
> On Fri, Feb 25, 2011 at 2:22
Great work!
Vishy and termie got jenkins launching ubuntu+kvm and running smoke tests.
There are a few isssues left but I'm excited to increase coverage.
We'd like to add coverage for rhel 5/6 and suse.
http://ansolabs.no-ip.org:9000/
We'll write an email about how it works so others can run or
Perhaps the articles can be added to docs somewhere to nova.openstack.org,
the wiki, or docs.openstack.org?
Vishy is going to be working on the chef scripts integrating changes by Mike
Ray. (We'd rather not have two active chef recipe sets)
On Feb 21, 2011 12:29 PM, "Jay Pipes" wrote:
__
Jay,
Agree that openstack api coverage top priority in added smoketests.
The work needed done on vagrant (vish led it and wrote about it a bit at
ansolabs.com/deploy) was a start to making something that worked outside
nasa - the multinode work was so it would work on any *nix box. Nasa's
testing
Catching up as well...
On Thu, Feb 17, 2011 at 2:57 PM, Jay Pipes wrote:
> The Anso team has told me that they run the smoketests regularly, but
> I would assume they only run these smoketests against a test cluster
> that mimicks the Nebula environment. Devin and termie can correct me
> if I'm w
80 matches
Mail list logo
