Hey Joe,

In response to your question around our plans.    I will gladly shed some light 
in that area.

I apologize for the delayed response as I was waiting to confirm information 
prior to responding.

To start we have been stabilizing what we have in place today, and are in the 
process of adding additional checks and tests below tempest to ensure we do not 
put Python modules in place that will break our tempest runs.

Additionally we are in the process of moving to a complete build from source  
of the entire python stack for hyper-v nodes in the tempest runs.   Today we 
have a partial source configuration using Python public binaries for Windows as 
a the starting point with only some of the required modules being provided by 
binaries and others being built on the fly.

>From a hardware perspective we have implemented plans and are currently in the 
>hardware acquisition phase of building out a completely new deployment of the 
>CI on hardware that is magnitudes above what we are currently using.   This 
>new deployment will be hosted in an Official MS Datacenter and have hardware 
>supported by onsite techs.

The timeline for the physical provisioning to be completed will be sometime 
this May/June.   Because we are making such a progression forward in both 
physical compute power (200 Azure Quality hosts) and networking infrastructure 
(Multiple 10G/1G Interfaces per host) we are going to take some time optimizing 
the deployment so that we can achieve the most stable and performant Tempest 
run. I am optimistic that the new deployment will be operational sometime 
between the J2 and J3 timeframe.

This is the Short Term Plan.

Longer Term is still in development and I will share more about it once details 
are finalized.

Please feel free to reach out directly if you have any questions.

Best,

P

Peter J. Pouliot CISSP
Sr. SDET OpenStack
Microsoft
New England Research & Development Center
1 Memorial Drive
Cambridge, MA 02142
P: 1.(857).4536436
E: ppoul...@microsoft.com<mailto:ppoul...@microsoft.com>


From: Joe Gordon <joe.gord...@gmail.com<mailto:joe.gord...@gmail.com>>
Reply-To: 
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, April 1, 2014 at 4:02 PM
To: 
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] Hyper-V CI is broken




On Tue, Apr 1, 2014 at 11:51 AM, Alessandro Pilotti 
<apilo...@cloudbasesolutions.com<mailto:apilo...@cloudbasesolutions.com>> wrote:
Hi Joe,

We have issues with Nova resize that we are troubleshooting. If we don't find 
the root cause by today we'll temporarily skip the resize tests.

How long has resize been broken for? Is there a bug for it? Can we skip resize 
for now and add that bug to the known issues for icehouse. That way we can say 
hyper-v is working for everything but resize as apposed to the current status..


Thanks,

Alessandro




On 01 Apr 2014, at 21:27, Joe Gordon 
<joe.gord...@gmail.com<mailto:joe.gord...@gmail.com>> wrote:

Hi Hyper-V CI maintainers,
CC: openstack-dev

As per [0] Hyper-V CI is failing 100% of the time, what are the blockers in 
making this work again? are there any outstanding nova patches that will fix 
this? We would like to hyper-v working in icehouse, and if not we will be 
forced to add a note saying it doesn't work to the icehouse release notes [1].


[0] http://www.rcbops.com/gerrit/reports/nova-cireport.html
[1] https://wiki.openstack.org/wiki/ReleaseNotes/Havana#Known_Issues_2
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to