Re: [Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session

[Blair Bethwaite]

Hi Jay,

On 4 April 2017 at 00:20, Jay Pipes  wrote:
> However, implementing the above in any useful fashion requires that Blazar
> be placed *above* Nova and essentially that the cloud operator turns off
> access to Nova's  POST /servers API call for regular users. Because if not,
> the information that Blazar acts upon can be simply circumvented by any user
> at any time.

That's something of an oversimplification. A reservation system
outside of Nova could manipulate Nova host-aggregates to "cordon off"
infrastructure from on-demand access (I believe Blazar already uses
this approach), and it's not much of a jump to imagine operators being
able to twiddle the available reserved capacity in a finite cloud so
that reserved capacity can be offered to the subset of users/projects
that need (or perhaps have paid for) it. Such a reservation system
would even be able to backfill capacity between reservations. At the
end of the reservation the system cleans-up any remaining instances
and preps for the next reservation.

The are a couple of problems with putting this outside of Nova though.
The main issue is that pre-emptible/spot type instances can't be
accommodated within the on-demand cloud capacity. You could have the
reservation system implementing this feature, but that would then put
other scheduling constraints on the cloud in order to be effective
(e.g., there would need to be automation changing the size of the
on-demand capacity so that the maximum pre-emptible capacity was
always available). The other issue (admittedly minor, but still a
consideration) is that it's another service - personally I'd love to
see Nova support these advanced use-cases directly.

-- 
Cheers,
~Blairo

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

Re: [Openstack-operators] FW: Can Windows 8, Windows Server 2003 and Windows Server 2008 be deployed on openstack kilo

[Adrian Vladu]

Sure, you are correct, the image properties are a must when it comes to 
limiting the failure occurrence, by setting the "os_type=windows" glance image 
property.

I was focusing on the requirements to make it run in the first place - exposing 
the required kvm CPU flags (+cx8,+cx1 in case of win2012/win8 and 
+cx16,+lahf_lm,+3dnow for win10/2016/nano) and VirtIO drivers.

Thank you,
Adrian Vladu

-Original Message-
From: Steve Gordon [mailto:sgor...@redhat.com] 
Sent: Monday, April 3, 2017 6:39 PM
To: Adrian Vladu 
Cc: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] FW: Can Windows 8, Windows Server 2003 and 
Windows Server 2008 be deployed on openstack kilo

- Original Message -
> From: "Adrian Vladu" 
> To: openstack-operators@lists.openstack.org
> Sent: Monday, April 3, 2017 7:50:01 AM
> Subject: [Openstack-operators] FW:  Can Windows 8, Windows Server 2003 
> and Windows Server 2008 be deployed on openstack kilo
> 
> Hello,
> 
> Windows 8 and Windows Server 2008 Standard can be deployed on 
> OpenStack with KVM (QEMU is not supported) as a hypervisor, if you 
> have the required Windows CPU flags exposed to the virtual machine. 
> “os-variant” is irrelevant in the OpenStack case, as this is a virt-install 
> terminology.

I wouldn't go as far as to say this is irrelevant, in that you do still need to 
use the image properties (as covered in the blog Tim provided) to enable the 
Hyper-V enlightenment features that Libvirt/QEMU is able to support for Windows 
guests - which is in effect doing the same thing as using the equivalent 
os-variant values with virt-install.

-Steve

> OpenStack uses libvirt as a driver, and the cpu_model and cpu_flags 
> are the important configuration options in this case. More info here:
> https://ask.cloudbase.it/question/1125/problem-booting-from-the-window
> s-2012-r2-image/
> 
> On OpenStack, you can use Cloudbase-init as the provisioning agent for 
> the Windows instances in the same way you use cloud-init for the Linux ones:
> https://github.com/openstack/cloudbase-init
> 
> Windows Server 2003 is not supported anymore by MSFT:
> https://www.microsoft.com/en-us/cloud-platform/windows-server-2003
> AFAIK, Windows 2003 instances can work on KVM and the Fedora VirtIO 
> drivers for this OS are still being offered in the stable releases:
> https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archi
> ve-virtio/virtio-win-0.1.126-2/
> 
> Thank you,
> Adrian Vladu
> From: Tim Bell [mailto:tim.b...@cern.ch]
> Sent: luni, 3 aprilie 2017 14:13
> To: openstack-operators
>  sts.openstack.org>>
> Subject: Re: [Openstack-operators] Can Windows 8, Windows Server 2003 
> and Windows Server 2008 be deployed on openstack kilo
> 
> The metadata settings on the images is important to inform KVM of the 
> guest operating system. We’ve put our experiences with a recent issue 
> at 
> https://openstack-in-production.blogspot.ch/2017/02/ostype-property-fo
> r-windows-images-on.html
> 
> Tim
> 
> From: "Van Leeuwen, Robert"
> >
> Date: Monday, 3 April 2017 at 12:54
> To: Anwar Durrani 
> >,
> openstack-operators
>  sts.openstack.org>>
> Subject: Re: [Openstack-operators] Can Windows 8, Windows Server 2003 
> and Windows Server 2008 be deployed on openstack kilo
> 
> Hello,
> 
> Its not really OpenStack related but it depends on your virtualization stack.
> Assuming its OpenStack with KVM:
> https://www.linux-kvm.org/page/Guest_Support_Status#Windows_Family
> 
> Note that you might have some interesting times with the licensing.
> From what I have understood (I am not a license specialist so take 
> this with a pile of salt):
> You must have a Windows (datacenter?) license per hypervisor that can 
> potentially run Windows instances.
> 
> Cheers,
> Robert
> 
> 
> From: Anwar Durrani 
> >
> Date: Monday, April 3, 2017 at 11:35 AM
> To: openstack-operators
>  sts.openstack.org>>
> Subject: [Openstack-operators] Can Windows 8, Windows Server 2003 and 
> Windows Server 2008 be deployed on openstack kilo
> 
> Hi Team,
> 
> I am curious to know if Windows 8 Pro, Windows Server 2003 Std and 
> Windows Server 2008 Std can be deployed to openstack or not ? if Yes 
> then what would be os-variant for the same ?
> 
> --
> Thanks & regards,
> Anwar M. Durrani
> +91-9923205011
> 
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator
> s
> 

--
Steve Gordon,
Principal 

Re: [Openstack-operators] FW: Can Windows 8, Windows Server 2003 and Windows Server 2008 be deployed on openstack kilo

[Steve Gordon]

- Original Message -
> From: "Adrian Vladu" 
> To: openstack-operators@lists.openstack.org
> Sent: Monday, April 3, 2017 7:50:01 AM
> Subject: [Openstack-operators] FW:  Can Windows 8, Windows Server 2003 and 
> Windows Server 2008 be deployed on
> openstack kilo
> 
> Hello,
> 
> Windows 8 and Windows Server 2008 Standard can be deployed on OpenStack with
> KVM (QEMU is not supported) as a hypervisor, if you have the required
> Windows CPU flags exposed to the virtual machine. “os-variant” is irrelevant
> in the OpenStack case, as this is a virt-install terminology.

I wouldn't go as far as to say this is irrelevant, in that you do still need to 
use the image properties (as covered in the blog Tim provided) to enable the 
Hyper-V enlightenment features that Libvirt/QEMU is able to support for Windows 
guests - which is in effect doing the same thing as using the equivalent 
os-variant values with virt-install.

-Steve

> OpenStack uses libvirt as a driver, and the cpu_model and cpu_flags are the
> important configuration options in this case. More info here:
> https://ask.cloudbase.it/question/1125/problem-booting-from-the-windows-2012-r2-image/
> 
> On OpenStack, you can use Cloudbase-init as the provisioning agent for the
> Windows instances in the same way you use cloud-init for the Linux ones:
> https://github.com/openstack/cloudbase-init
> 
> Windows Server 2003 is not supported anymore by MSFT:
> https://www.microsoft.com/en-us/cloud-platform/windows-server-2003
> AFAIK, Windows 2003 instances can work on KVM and the Fedora VirtIO drivers
> for this OS are still being offered in the stable releases:
> https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.126-2/
> 
> Thank you,
> Adrian Vladu
> From: Tim Bell [mailto:tim.b...@cern.ch]
> Sent: luni, 3 aprilie 2017 14:13
> To: openstack-operators
> >
> Subject: Re: [Openstack-operators] Can Windows 8, Windows Server 2003 and
> Windows Server 2008 be deployed on openstack kilo
> 
> The metadata settings on the images is important to inform KVM of the guest
> operating system. We’ve put our experiences with a recent issue at
> https://openstack-in-production.blogspot.ch/2017/02/ostype-property-for-windows-images-on.html
> 
> Tim
> 
> From: "Van Leeuwen, Robert"
> >
> Date: Monday, 3 April 2017 at 12:54
> To: Anwar Durrani >,
> openstack-operators
> >
> Subject: Re: [Openstack-operators] Can Windows 8, Windows Server 2003 and
> Windows Server 2008 be deployed on openstack kilo
> 
> Hello,
> 
> Its not really OpenStack related but it depends on your virtualization stack.
> Assuming its OpenStack with KVM:
> https://www.linux-kvm.org/page/Guest_Support_Status#Windows_Family
> 
> Note that you might have some interesting times with the licensing.
> From what I have understood (I am not a license specialist so take this with
> a pile of salt):
> You must have a Windows (datacenter?) license per hypervisor that can
> potentially run Windows instances.
> 
> Cheers,
> Robert
> 
> 
> From: Anwar Durrani >
> Date: Monday, April 3, 2017 at 11:35 AM
> To: openstack-operators
> >
> Subject: [Openstack-operators] Can Windows 8, Windows Server 2003 and Windows
> Server 2008 be deployed on openstack kilo
> 
> Hi Team,
> 
> I am curious to know if Windows 8 Pro, Windows Server 2003 Std and Windows
> Server 2008 Std can be deployed to openstack or not ? if Yes then what would
> be os-variant for the same ?
> 
> --
> Thanks & regards,
> Anwar M. Durrani
> +91-9923205011
> 
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> 

-- 
Steve Gordon,
Principal Product Manager,
Red Hat OpenStack Platform

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

Re: [Openstack-operators] [scientific] Resource reservation requirements (Blazar) - Forum session

[Joe Topjian]

On Mon, Apr 3, 2017 at 8:20 AM, Jay Pipes  wrote:

> On 04/01/2017 08:32 PM, Joe Topjian wrote:
>
>> On Sat, Apr 1, 2017 at 5:21 PM, Matt Riedemann > > wrote:
>>
>> On 4/1/2017 8:36 AM, Blair Bethwaite wrote:
>>
>> Hi all,
>>
>> The below was suggested for a Forum session but we don't yet have
>> a
>> submission or name to chair/moderate. I, for one, would certainly
>> be
>> interested in providing input. Do we have any owners out there?
>>
>> Resource reservation requirements:
>> ==
>> The Blazar project [https://wiki.openstack.org/wiki/Blazar
>> ] has been
>> revived following Barcelona and will soon release a new version.
>> Now
>> is a good time to get involved and share requirements with the
>> community. Our development priorities are described through
>> Blueprints
>> on Launchpad: https://blueprints.launchpad.net/blazar
>> 
>>
>> In particular, support for pre-emptible instances could be
>> combined
>> with resource reservation to maximize utilization on unreserved
>> resources.+1
>>
>>
>> Regarding resource reservation, please see this older Nova spec
>> which is related:
>>
>> https://review.openstack.org/#/c/389216/
>> 
>>
>> And see the points that Jay Pipes makes in that review. Before
>> spending a lot of time reviving the project, I'd encourage people to
>> read and digest the points made in that review and if there
>> responses or other use cases then let's discuss them *before*
>> bringing a service back from the dead and assume it will be
>> integrated into the other projects.
>>
>> This is appreciated. I'll describe the way I've seen Blazar used and I
>> believe it's quite different than the above slot reservation as well as
>> spot instance support, but please let me know if I am incorrect or if
>> there have been other discussions about this use-case elsewhere:
>>
>> A research group has a finite amount of specialized hardware and there
>> are more people wanting to use this hardware than what's currently
>> available. Let's use high performance GPUs as an example. The group is
>> OK with publishing the amount of hardware they have available (normally
>> this is hidden as best as possible). By doing this, a researcher can use
>> Blazar as sort of a community calendar, see that there are 3 GPU nodes
>> available for the week of April 3, and reserve them for that time period.
>>
>
> Yeah, I totally understand this use case.
>
> However, implementing the above in any useful fashion requires that Blazar
> be placed *above* Nova and essentially that the cloud operator turns off
> access to Nova's  POST /servers API call for regular users. Because if not,
> the information that Blazar acts upon can be simply circumvented by any
> user at any time.
>
> In other words, your "3 GPU nodes available for the week of April 3" can
> change at any time by a user that goes and launches instances that consumes
> those 3 GPU nodes.
>
> If you have a certain type of OpenStack deployment that isn't multi-user
> and where the only thing that launches instances is an
> automation/orchestration tool (in other words, an NFV MANO system), the
> reservation concepts works great -- because you don't have pesky users that
> can sidestep the system and actually launch instances that would impact
> reserved consumables.
>
> However, if you *do* have normal users of your cloud -- as most scientific
> deployments must have -- then I'm afraid the only way to make this work is
> to have users *only* use the Blazar API to reserve instances and
> essentially shut off the normal Nova POST /servers API.
>
> Does that make sense?
>

Ah, yes, indeed it does. Thanks, Jay.
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] FW: Can Windows 8, Windows Server 2003 and Windows Server 2008 be deployed on openstack kilo

[Adrian Vladu]

Hello,

Windows 8 and Windows Server 2008 Standard can be deployed on OpenStack with 
KVM (QEMU is not supported) as a hypervisor, if you have the required Windows 
CPU flags exposed to the virtual machine. “os-variant” is irrelevant in the 
OpenStack case, as this is a virt-install terminology.

OpenStack uses libvirt as a driver, and the cpu_model and cpu_flags are the 
important configuration options in this case. More info here: 
https://ask.cloudbase.it/question/1125/problem-booting-from-the-windows-2012-r2-image/

On OpenStack, you can use Cloudbase-init as the provisioning agent for the 
Windows instances in the same way you use cloud-init for the Linux ones: 
https://github.com/openstack/cloudbase-init

Windows Server 2003 is not supported anymore by MSFT: 
https://www.microsoft.com/en-us/cloud-platform/windows-server-2003
AFAIK, Windows 2003 instances can work on KVM and the Fedora VirtIO drivers for 
this OS are still being offered in the stable releases: 
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.126-2/

Thank you,
Adrian Vladu
From: Tim Bell [mailto:tim.b...@cern.ch]
Sent: luni, 3 aprilie 2017 14:13
To: openstack-operators 
>
Subject: Re: [Openstack-operators] Can Windows 8, Windows Server 2003 and 
Windows Server 2008 be deployed on openstack kilo

The metadata settings on the images is important to inform KVM of the guest 
operating system. We’ve put our experiences with a recent issue at 
https://openstack-in-production.blogspot.ch/2017/02/ostype-property-for-windows-images-on.html

Tim

From: "Van Leeuwen, Robert" 
>
Date: Monday, 3 April 2017 at 12:54
To: Anwar Durrani >, 
openstack-operators 
>
Subject: Re: [Openstack-operators] Can Windows 8, Windows Server 2003 and 
Windows Server 2008 be deployed on openstack kilo

Hello,

Its not really OpenStack related but it depends on your virtualization stack.
Assuming its OpenStack with KVM:
https://www.linux-kvm.org/page/Guest_Support_Status#Windows_Family

Note that you might have some interesting times with the licensing.
From what I have understood (I am not a license specialist so take this with a 
pile of salt):
You must have a Windows (datacenter?) license per hypervisor that can 
potentially run Windows instances.

Cheers,
Robert


From: Anwar Durrani >
Date: Monday, April 3, 2017 at 11:35 AM
To: openstack-operators 
>
Subject: [Openstack-operators] Can Windows 8, Windows Server 2003 and Windows 
Server 2008 be deployed on openstack kilo

Hi Team,

I am curious to know if Windows 8 Pro, Windows Server 2003 Std and Windows 
Server 2008 Std can be deployed to openstack or not ? if Yes then what would be 
os-variant for the same ?

--
Thanks & regards,
Anwar M. Durrani
+91-9923205011

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

Re: [Openstack-operators] Can Windows 8, Windows Server 2003 and Windows Server 2008 be deployed on openstack kilo

[Van Leeuwen, Robert]

Hello,

Its not really OpenStack related but it depends on your virtualization stack.
Assuming its OpenStack with KVM:
https://www.linux-kvm.org/page/Guest_Support_Status#Windows_Family

Note that you might have some interesting times with the licensing.
From what I have understood (I am not a license specialist so take this with a 
pile of salt):
You must have a Windows (datacenter?) license per hypervisor that can 
potentially run Windows instances.

Cheers,
Robert


From: Anwar Durrani 
Date: Monday, April 3, 2017 at 11:35 AM
To: openstack-operators 
Subject: [Openstack-operators] Can Windows 8, Windows Server 2003 and Windows 
Server 2008 be deployed on openstack kilo

Hi Team,

I am curious to know if Windows 8 Pro, Windows Server 2003 Std and Windows 
Server 2008 Std can be deployed to openstack or not ? if Yes then what would be 
os-variant for the same ?

--
Thanks & regards,
Anwar M. Durrani
+91-9923205011

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

[Openstack-operators] Can Windows 8, Windows Server 2003 and Windows Server 2008 be deployed on openstack kilo

[Anwar Durrani]

Hi Team,

I am curious to know if Windows 8 Pro, Windows Server 2003 Std and Windows
Server 2008 Std can be deployed to openstack or not ? if Yes then what
would be os-variant for the same ?

-- 
Thanks & regards,
Anwar M. Durrani
+91-9923205011

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