On 08/18/2014 05:13 PM, Charles Hsu wrote:
> HI,
>
> Here is a wiki page for our cluster
> https://wiki.openstack.org/wiki/ThirdPartySystems/SwiftStack_Cluster_CI
>
> Thanks
>
And we have consensus around SwiftStack Cluster CI and swiftstack-cluster-ci
Thanks,
Anita.
>
> On Sun, Aug 17, 2014 a
HI,
Here is a wiki page for our cluster
https://wiki.openstack.org/wiki/ThirdPartySystems/SwiftStack_Cluster_CI
Thanks
On Sun, Aug 17, 2014 at 11:10 PM, Charles Hsu wrote:
> Hi,
>
> We're try to setup a CI cluster for swift, please help us to create a
> gerrit account.
> Here is required info
Hi Jim,
I have fixed this issue, please check the
https://review.openstack.org/#/c/112714/
and left a link of "dsvm-tempest-full Failure" of IBM Storwize CI, it will
link to
http://dal05.objectstorage.softlayer.net/v1/AUTH_58396f85-2c60-47b9-aaf8-e03bc24a1a6f/IBMStorwizeCI/14/112714/8/check/
Hi,
We're try to setup a CI cluster for swift, please help us to create a
gerrit account.
Here is required information.
1. SSH Public Key
ssh-rsa
B3NzaC1yc2EDAQABAAABAQCy7Dt+tiqeQZgFaFoRi1ItRad0/pt/9ziR/sfh0Vs6Y0vJVI6H+FG4WJyFh3lXcuwMDx2zuVMIdsd+Svq8fYsMsz/RLeF7NCMq7+BGB4CTKq1mAte1cADGO
On 2014-08-18 20:40:48 +0300 (+0300), Ivan Kolodyazhny wrote:
[...]
> I'm looking for something like following:
>
> 1) run my Third Party CI for all patch-sets in Cinder
> 2) run my Third Party CI (Cinder + Ceph backend) for Nova only if it
> changes nova/virt/libvirt/rbd.py module.
>
> Does such
Hi everyone,
The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting on Tuesday August 19th, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone interested
Hi All,
I'm working on Third Party CI for Cinder and I've got several issues with
Zuul configuration.
Third Party CI should run dsvm-tempest-full job to test Cinder driver in my
case. It means, that all components should work well, not only Cinder.
E.g.: I'm working on Cinder + Ceph integration
I'm not sure why, but the default tenant network type was changed to vxlan.
[1]
You now need to specify Q_ML2_TENANT_NETWORK_TYPE=vlan
1.
https://github.com/openstack-dev/devstack/commit/8feaf6c9516094df58df84479d73779e87a79264
On Mon, Aug 18, 2014 at 9:35 AM, Parikshit Manur wrote:
> Hi All
When you don't specify it, the default network type is:
(from lib/neutron_plugins/ml2)
Q_ML2_TENANT_NETWORK_TYPE=${Q_ML2_TENANT_NETWORK_TYPE:-"vxlan"}
You can try specifying that as "vlan" in your local.conf file and see what
happens.
-Brian
BTW, this probably should have just gone to openst..
On 8/18/2014 12:35 PM, Parikshit Manur wrote:
> Start of q-svc in devstack fails with error message “No type
> driver for tenant network_type: vxlan. Service terminated!”. I have not
> choosen vxlan as ML2 type driver in localrc.
Devstack now defaults to vxlan for the tenant netwo
Hi All,
Start of q-svc in devstack fails with error message "No type
driver for tenant network_type: vxlan. Service terminated!". I have not choosen
vxlan as ML2 type driver in localrc. I have added the details of localrc file
for my setup below for reference. Can you please poi
On 2014-08-17 23:53:12 -0700 (-0700), daya kamath wrote:
[...]
> openstack-infra does not get updated as part of the gate jobs
[...]
Right, we use puppet to continuously apply that configuration to our
durable workers and nodepool templates.
--
Jeremy Stanley
Congrats Sukhdev :) That's no small feat.
On 7 August 2014 03:41, Sukhdev Kapur wrote:
> I am looking into the scenario tests. Having some issues with them. Will
> soon be adding a few to the test suite.
>
This is also where I'm at with the Tail-f CI driver. I am running API tests
stably now bu
13 matches
Mail list logo
