In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal. Thanks.
On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal.
In oVirt guests aren't tied to a host by default (although you can set them to run only on a specific host if you want). The closest thing I can think of would be the High Availability features (VM->Edit). oVirt will try to restart highly available VMs if they go down. You can also set the priority for migration and restart in that pane. Hopefully a combination of host pinning and the high availability settings will get you close enough to where you want to be. Otherwise, you could always do some scripting with the ovirt REST API using the SDK or CLI. -- Adam Litke
On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:
On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal.
In oVirt guests aren't tied to a host by default (although you can set them to run only on a specific host if you want). The closest thing I can think of would be the High Availability features (VM->Edit). oVirt will try to restart highly available VMs if they go down. You can also set the priority for migration and restart in that pane. Hopefully a combination of host pinning and the high availability settings will get you close enough to where you want to be.
Otherwise, you could always do some scripting with the ovirt REST API using the SDK or CLI.
If you had the VMware migration extra add-on you could have hosts move as needed so they were not tied to any host either but we could set a startup order and specify auto, manual so that once the host started the VMs were brought up as specified no matter what host they were running on. I am running hosted-engine deployment with the Engine VM on the host. I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first. It would be nice if oVirt added this feature as it's really required for large installations and is a help for any size installation, even small ones.
On 6-4-2016 21:10, Brett I. Holcomb wrote:
On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:
On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal.
In oVirt guests aren't tied to a host by default (although you can set them to run only on a specific host if you want). The closest thing I can think of would be the High Availability features (VM->Edit). oVirt will try to restart highly available VMs if they go down. You can also set the priority for migration and restart in that pane. Hopefully a combination of host pinning and the high availability settings will get you close enough to where you want to be.
Otherwise, you could always do some scripting with the ovirt REST API using the SDK or CLI.
If you had the VMware migration extra add-on you could have hosts move as needed so they were not tied to any host either but we could set a startup order and specify auto, manual so that once the host started the VMs were brought up as specified no matter what host they were running on.
I am running hosted-engine deployment with the Engine VM on the host.
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
It would be nice if oVirt added this feature as it's really required for large installations and is a help for any size installation, even small ones.
Maybe there is a another way. It involves ovirt-shell and/or a sdk script. The idea is the create a custom property and set that to for example, y:01 or n:02 and yes that to read that back if the host comes up and start the vms if they have 'y' and use the number for ordering. If reading back the properties is a problem you might be able to 'use' the tagging feature todo something similar. You can always create a RFE on the ovirt bugtracker. Joop
On Wed, 2016-04-06 at 21:44 +0200, Joop wrote:
On 6-4-2016 21:10, Brett I. Holcomb wrote:
On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:
On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal.
In oVirt guests aren't tied to a host by default (although you can set them to run only on a specific host if you want). The closest thing I can think of would be the High Availability features (VM->Edit). oVirt will try to restart highly available VMs if they go down. You can also set the priority for migration and restart in that pane. Hopefully a combination of host pinning and the high availability settings will get you close enough to where you want to be.
Otherwise, you could always do some scripting with the ovirt REST API using the SDK or CLI.
If you had the VMware migration extra add-on you could have hosts move as needed so they were not tied to any host either but we could set a startup order and specify auto, manual so that once the host started the VMs were brought up as specified no matter what host they were running on.
I am running hosted-engine deployment with the Engine VM on the host.
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
It would be nice if oVirt added this feature as it's really required for large installations and is a help for any size installation, even small ones.
Maybe there is a another way. It involves ovirt-shell and/or a sdk script. The idea is the create a custom property and set that to for example, y:01 or n:02 and yes that to read that back if the host comes up and start the vms if they have 'y' and use the number for ordering. If reading back the properties is a problem you might be able to 'use' the tagging feature todo something similar.
You can always create a RFE on the ovirt bugtracker.
Joop
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users I'll do that. It's really a needed feature to make administration easier. I finally got the ovirt-shell connected with the help of this https://b ugzilla.redhat.com/show_bug.cgi?id=1186365. The silly thing can't handle no domain and the error doesn't tell you that. Oh, well. We'll play with this and then check out rest and SDK.
On Wed, 2016-04-06 at 21:44 +0200, Joop wrote:
On 6-4-2016 21:10, Brett I. Holcomb wrote:
On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:
On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal.
In oVirt guests aren't tied to a host by default (although you can set them to run only on a specific host if you want). The closest thing I can think of would be the High Availability features (VM->Edit). oVirt will try to restart highly available VMs if they go down. You can also set the priority for migration and restart in that pane. Hopefully a combination of host pinning and the high availability settings will get you close enough to where you want to be.
Otherwise, you could always do some scripting with the ovirt REST API using the SDK or CLI.
If you had the VMware migration extra add-on you could have hosts move as needed so they were not tied to any host either but we could set a startup order and specify auto, manual so that once the host started the VMs were brought up as specified no matter what host they were running on.
I am running hosted-engine deployment with the Engine VM on the host.
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
It would be nice if oVirt added this feature as it's really required for large installations and is a help for any size installation, even small ones.
Maybe there is a another way. It involves ovirt-shell and/or a sdk script. The idea is the create a custom property and set that to for example, y:01 or n:02 and yes that to read that back if the host comes up and start the vms if they have 'y' and use the number for ordering. If reading back the properties is a problem you might be able to 'use' the tagging feature todo something similar.
You can always create a RFE on the ovirt bugtracker.
Joop
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users I'll do that. It's really a needed feature to make administration easier. I finally got the ovirt-shell connected with the help of this https://b ugzilla.redhat.com/show_bug.cgi?id=1186365. The silly thing can't handle no domain and the error doesn't tell you that. Oh, well. We'll play with this and then check out the A
Hi,
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
The engine will try to keep the VM running. So if one host goes down, it will restart the VM on some other host automatically. We will also migrate the VM (or some other to free resources) when the current host gets too loaded. We do not require any migration addons, it just works. But of course we have usually more hosts in a cluster to make this possible. I do not really remember what happens when all hosts are restarted (power outage) though as that is quite special case. Regards -- Martin Sivak SLA / oVirt On Wed, Apr 6, 2016 at 9:10 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:
On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal.
In oVirt guests aren't tied to a host by default (although you can set them to run only on a specific host if you want). The closest thing I can think of would be the High Availability features (VM->Edit). oVirt will try to restart highly available VMs if they go down. You can also set the priority for migration and restart in that pane. Hopefully a combination of host pinning and the high availability settings will get you close enough to where you want to be.
Otherwise, you could always do some scripting with the ovirt REST API using the SDK or CLI.
If you had the VMware migration extra add-on you could have hosts move as needed so they were not tied to any host either but we could set a startup order and specify auto, manual so that once the host started the VMs were brought up as specified no matter what host they were running on.
I am running hosted-engine deployment with the Engine VM on the host.
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
It would be nice if oVirt added this feature as it's really required for large installations and is a help for any size installation, even small ones.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
Hi,
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
The engine will try to keep the VM running. So if one host goes down, it will restart the VM on some other host automatically. We will also migrate the VM (or some other to free resources) when the current host gets too loaded. We do not require any migration addons, it just works. But of course we have usually more hosts in a cluster to make this possible.
I do not really remember what happens when all hosts are restarted (power outage) though as that is quite special case.
Regards
-- Martin Sivak SLA / oVirt Thanks. I only have one host so who knows what will happen. I'm working on a script that will basically emulate what VMware does - start VMS in a given order at startup of the host/engine. I'll also file a feature request. On Wed, Apr 6, 2016 at 9:10 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
wrote:
On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:
On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal.
In oVirt guests aren't tied to a host by default (although you can set them to run only on a specific host if you want). The closest thing I can think of would be the High Availability features (VM->Edit). oVirt will try to restart highly available VMs if they go down. You can also set the priority for migration and restart in that pane. Hopefully a combination of host pinning and the high availability settings will get you close enough to where you want to be.
Otherwise, you could always do some scripting with the ovirt REST API using the SDK or CLI.
If you had the VMware migration extra add-on you could have hosts move as needed so they were not tied to any host either but we could set a startup order and specify auto, manual so that once the host started the VMs were brought up as specified no matter what host they were running on.
I am running hosted-engine deployment with the Engine VM on the host.
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
It would be nice if oVirt added this feature as it's really required for large installations and is a help for any size installation, even small ones.
_______________________________________________ Users mailing list
Users@ovirt.org> > http://lists.ovirt.org/mailman/listinfo/users
On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
Hi,
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
The engine will try to keep the VM running. So if one host goes down, it will restart the VM on some other host automatically. We will also migrate the VM (or some other to free resources) when the current host gets too loaded. We do not require any migration addons, it just works. But of course we have usually more hosts in a cluster to make this possible.
I do not really remember what happens when all hosts are restarted (power outage) though as that is quite special case.
Regards
-- Martin Sivak SLA / oVirt
Thanks. I only have one host so who knows what will happen. I'm working on a script that will basically emulate what VMware does - start VMS in a given order at startup of the host/engine. I'll also file a feature request.
Why do you care about the order? Isn't it enough to restart all the vms after a host was restarted? Nir
On Wed, Apr 6, 2016 at 9:10 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:
On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal.
In oVirt guests aren't tied to a host by default (although you can set them to run only on a specific host if you want). The closest thing I can think of would be the High Availability features (VM->Edit). oVirt will try to restart highly available VMs if they go down. You can also set the priority for migration and restart in that pane. Hopefully a combination of host pinning and the high availability settings will get you close enough to where you want to be.
Otherwise, you could always do some scripting with the ovirt REST API using the SDK or CLI.
If you had the VMware migration extra add-on you could have hosts move as needed so they were not tied to any host either but we could set a startup order and specify auto, manual so that once the host started the VMs were brought up as specified no matter what host they were running on.
I am running hosted-engine deployment with the Engine VM on the host.
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
It would be nice if oVirt added this feature as it's really required for large installations and is a help for any size installation, even small ones.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Actually this is used pretty regularly in VMware environments. For instance I've seen MSSQL systems running under AD credentials so they can access UNC shares. If the AD domain controllers aren't up prior to the database server starting up the MSSQL service won't start because it can't authenticate the user on the service. On Fri, Apr 8, 2016 at 9:25 AM Nir Soffer <nsoffer@redhat.com> wrote:
On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
Hi,
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
The engine will try to keep the VM running. So if one host goes down, it will restart the VM on some other host automatically. We will also migrate the VM (or some other to free resources) when the current host gets too loaded. We do not require any migration addons, it just works. But of course we have usually more hosts in a cluster to make this possible.
I do not really remember what happens when all hosts are restarted (power outage) though as that is quite special case.
Regards
-- Martin Sivak SLA / oVirt
Thanks. I only have one host so who knows what will happen. I'm working on a script that will basically emulate what VMware does - start VMS in a given order at startup of the host/engine. I'll also file a feature request.
Why do you care about the order?
Isn't it enough to restart all the vms after a host was restarted?
Nir
On Wed, Apr 6, 2016 at 9:10 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:
On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal.
In oVirt guests aren't tied to a host by default (although you can set them to run only on a specific host if you want). The closest thing I can think of would be the High Availability features (VM->Edit). oVirt will try to restart highly available VMs if they go down. You can also set the priority for migration and restart in that pane. Hopefully a combination of host pinning and the high availability settings will get you close enough to where you want to be.
Otherwise, you could always do some scripting with the ovirt REST API using the SDK or CLI.
If you had the VMware migration extra add-on you could have hosts move as needed so they were not tied to any host either but we could set a
startup
order and specify auto, manual so that once the host started the VMs were brought up as specified no matter what host they were running on.
I am running hosted-engine deployment with the Engine VM on the host.
I set highly available on, did not pin to any host, and also set the watchdog which should reset if they go down but I'm not sure that will start them if the host comes up and the VMs are not running. I'll look at the CLI first.
It would be nice if oVirt added this feature as it's really required for large installations and is a help for any size installation, even small ones.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- *Michael Kleinpaste* Senior Systems Administrator SharperLending, LLC. www.SharperLending.com Michael.Kleinpaste@SharperLending.com (509) 324-1230 Fax: (509) 324-1234
Actually this is used pretty regularly in VMware environments. For instance I've seen MSSQL systems running under AD credentials so they can access UNC shares. If the AD domain controllers aren't up prior to the database server starting up the MSSQL service won't start because it can't authenticate the user on the service.\ That was exactly what I had in one of my jobs where I had an AD domain for a University and we had several MSSQL servers that needed the AD credentials. Plus I had an IBM FileNet ECM system with several servers
On Fri, 2016-04-08 at 16:40 +0000, Michael Kleinpaste wrote: that had to be started in the correct order. With AD you need to have the domain controllers up and running or nothing works. Our Linux systems alsso had some that depended on others. If they weren't started in the correct order they had to be restarted again. And it's not really a VMware specific need but any environment whether it's physical or virtual needs as startup sequence. Before we virtualized we had a written procedure on what servers came up and in what order (and the reverse for a shutdown of the site). When moving to virtualization the virtualization system replaces people flipping switches with it's startup/shutdown order or it should.
On Fri, Apr 8, 2016 at 9:25 AM Nir Soffer <nsoffer@redhat.com> wrote:> > On Fri, Apr 8, 2016 at 7:17 PM, Brett I. Holcomb <biholcomb@l1049h.com> wrote:
On Fri, 2016-04-08 at 11:31 +0200, Martin Sivak wrote:
Hi,
I set highly available on, did not pin to any host, and also set the
watchdog which should reset if they go down but I'm not sure that will start
them if the host comes up and the VMs are not running. I'll look at the CLI
first.
The engine will try to keep the VM running. So if one host goes down,
it will restart the VM on some other host automatically. We will also
migrate the VM (or some other to free resources) when the current host
gets too loaded. We do not require any migration addons, it just
works. But of course we have usually more hosts in a cluster to make
this possible.
I do not really remember what happens when all hosts are restarted
(power outage) though as that is quite special case.
Regards
--
Martin Sivak
SLA / oVirt
Thanks. I only have one host so who knows what will happen. I'm working on
a script that will basically emulate what VMware does - start VMS in a given
order at startup of the host/engine. I'll also file a feature request.
Why do you care about the order?
Isn't it enough to restart all the vms after a host was restarted?
Nir
On Wed, Apr 6, 2016 at 9:10 PM, Brett I. Holcomb <biholcomb@l1049h.com>
wrote:
On Wed, 2016-04-06 at 13:42 -0400, Adam Litke wrote:
On 06/04/16 01:46 -0400, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and
define the order. Is that doable in oVirt? The only thing I've seen
is the watchdog and tell it to reset but nothing that allows me to
define who starts up when and if they autostart. I assume it's there
but I must be missing it or haven't found it in the web portal.
In oVirt guests aren't tied to a host by default (although you can set
them to run only on a specific host if you want). The closest thing I
can think of would be the High Availability features (VM->Edit).
oVirt will try to restart highly available VMs if they go down. You
can also set the priority for migration and restart in that pane.
Hopefully a combination of host pinning and the high availability
settings will get you close enough to where you want to be.
Otherwise, you could always do some scripting with the ovirt REST API
using the SDK or CLI.
If you had the VMware migration extra add-on you could have hosts move as
needed so they were not tied to any host either but we could set a startup
order and specify auto, manual so that once the host started the VMs were
brought up as specified no matter what host they were running on.
I am running hosted-engine deployment with the Engine VM on the host.
I set highly available on, did not pin to any host, and also set the
watchdog which should reset if they go down but I'm not sure that will start
them if the host comes up and the VMs are not running. I'll look at the CLI
first.
It would be nice if oVirt added this feature as it's really required for
large installations and is a help for any size installation, even small
ones.
_______________________________________________
Users mailing list
Users@ovirt.org
_______________________________________________
Users mailing list
Users@ovirt.org
_______________________________________________
Users mailing list
Users@ovirt.org
-- Michael Kleinpaste Senior Systems Administrator SharperLending, LLC. www.SharperLending.com Michael.Kleinpaste@SharperLending.com (509) 324-1230 Fax: (509) 324-1234
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --WP7x3STPIwkDc8wFTwloJwjArJ1q12vpP Content-Type: multipart/mixed; boundary="n1rUgT8Dla01a2n8NEIXploSiKs66WsxC" From: Sven Kieske <svenkieske@gmail.com> To: users@ovirt.org Message-ID: <5708A626.5030901@gmail.com> Subject: Re: [ovirt-users] Autostart VMS References: <1459921611.2689.292.camel@l1049h.com> In-Reply-To: <1459921611.2689.292.camel@l1049h.com> --n1rUgT8Dla01a2n8NEIXploSiKs66WsxC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 06.04.2016 07:46, Brett I. Holcomb wrote:
In VMware we could setup guests to autostart when the host started and define the order. Is that doable in oVirt? The only thing I've seen is the watchdog and tell it to reset but nothing that allows me to define who starts up when and if they autostart. I assume it's there but I must be missing it or haven't found it in the web portal.
See this long standing bug: https://bugzilla.redhat.com/show_bug.cgi?id=3D1166657 also searching this ML for "autostart" and "VM" turns up this same discussion every few months. sadly no dev seems to grasp the importance of this feature, so it's always rationalsed that it's not needed or the HA feature is enough (it isn't). I don't know why the already implemented libvirt autostart feature does not get simply passed through. This feature was at least requested by 4 or 5 different people, to no ava= il. you might CC yourself to the bugreport(RFE) and vote on it, maybe this way it will get some traction. kind regards Sven --n1rUgT8Dla01a2n8NEIXploSiKs66WsxC-- --WP7x3STPIwkDc8wFTwloJwjArJ1q12vpP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBCAAGBQJXCKZCAAoJEAq0kGAWDrqlSP4L/0Y3WP6z0KEn3ewtUAdU1UOD zcGsjJrpc6Cs4WxUAlzz0WrGQvxKcxhwex+RNAyyZKBQo0T8rWDjRMvOaJiRMItu le4igv6NIjTCh9aTbFDx/fu9FRdRinmOvsZr6eIo1+gAC5oX/yhxEUTFP9Vlq+KK k5YU1c2smtN3cnAkIUzcJf+sRmSv5GqzNiDLc27UAYEus8SsdMj7G7r6ARtwhwEa Ko2JNeCAyqEV96Y7IRmR9wXjhjtbtuzP5P4zDcIrMATEy5581opLkCqQ2H8IWjcu bEXwpJRXkGdz/e32mHLss4LEVyAsGyVmW+rFZ4mi7mQl75qDw6YA4hBFyaNjfP5f PqIaypI1ZMaEV64fy26NmaBAk9f/ZVRfZ2yHDZwdI77KwAauX6QxbW5nqqomgOgJ LvVAXbR2LemA9AnmFfg+seeCy5eNPcJYdVkFGMkfoN+vV7zIbxwOVzeLxj8wyFaX hiELM2+VKt73td8193w+iMg1ccGg/urJtBhtjWlTVQ== =EhAp -----END PGP SIGNATURE----- --WP7x3STPIwkDc8wFTwloJwjArJ1q12vpP--
--_000_1460209771158938camelacroniscom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SSdkIGxpa2UgdG8gc2VlIHRoZSBhdXRvc3RhcnQgZmVhdHVyZSBhcyB3ZWxsLiBJbiBteSBjYXNl IEkgbmVlZCB0byBhdXRvc3RhcnQgYSB2aXJ0dWFsIHJvdXRlciBWTSBhdCByZW1vdGUgc2l0ZS4g VGhlIGlzc3VlIGlzIHRoYXQgb1ZpcnQgY2FuJ3Qgc2VlIHRoZSByZW1vdGUgaG9zdCB1bnRpbCB0 aGUgdmlydHVhbCByb3V0ZXIgaXMgc3RhcnRlZCBvbiB0aGlzIGhvc3QuIFNvIEhBIGlzIG5vdCBh biBvcHRpb24uDQoNCk9uIFNhdCwgMjAxNi0wNC0wOSBhdCAwODo1MCArMDIwMCwgU3ZlbiBLaWVz a2Ugd3JvdGU6DQoNCk9uIDA2LjA0LjIwMTYgMDc6NDYsIEJyZXR0IEkuIEhvbGNvbWIgd3JvdGU6 DQoNCg0KSW4gVk13YXJlIHdlIGNvdWxkIHNldHVwIGd1ZXN0cyB0byBhdXRvc3RhcnQgd2hlbiB0 aGUgaG9zdCBzdGFydGVkIGFuZA0KZGVmaW5lIHRoZSBvcmRlci4gIElzIHRoYXQgZG9hYmxlIGlu IG9WaXJ0PyAgVGhlIG9ubHkgdGhpbmcgSSd2ZSBzZWVuDQppcyB0aGUgd2F0Y2hkb2cgYW5kIHRl bGwgaXQgdG8gcmVzZXQgYnV0IG5vdGhpbmcgdGhhdCBhbGxvd3MgbWUgdG8NCmRlZmluZSB3aG8g c3RhcnRzIHVwIHdoZW4gYW5kIGlmIHRoZXkgYXV0b3N0YXJ0LiAgSSBhc3N1bWUgaXQncyB0aGVy ZQ0KYnV0IEkgbXVzdCBiZSBtaXNzaW5nIGl0IG9yIGhhdmVuJ3QgZm91bmQgaXQgaW4gdGhlIHdl YiBwb3J0YWwuDQoNCg0KDQpTZWUgdGhpcyBsb25nIHN0YW5kaW5nIGJ1ZzoNCg0KaHR0cHM6Ly9i dWd6aWxsYS5yZWRoYXQuY29tL3Nob3dfYnVnLmNnaT9pZD0xMTY2NjU3DQoNCmFsc28gc2VhcmNo aW5nIHRoaXMgTUwgZm9yICJhdXRvc3RhcnQiIGFuZCAiVk0iDQoNCnR1cm5zIHVwIHRoaXMgc2Ft ZSBkaXNjdXNzaW9uIGV2ZXJ5IGZldyBtb250aHMuDQoNCnNhZGx5IG5vIGRldiBzZWVtcyB0byBn cmFzcCB0aGUgaW1wb3J0YW5jZSBvZiB0aGlzIGZlYXR1cmUsIHNvIGl0J3MNCmFsd2F5cyByYXRp b25hbHNlZCB0aGF0IGl0J3Mgbm90IG5lZWRlZCBvciB0aGUgSEEgZmVhdHVyZSBpcyBlbm91Z2gg KGl0DQppc24ndCkuDQoNCkkgZG9uJ3Qga25vdyB3aHkgdGhlIGFscmVhZHkgaW1wbGVtZW50ZWQg bGlidmlydCBhdXRvc3RhcnQgZmVhdHVyZQ0KZG9lcyBub3QgZ2V0IHNpbXBseSBwYXNzZWQgdGhy b3VnaC4NCg0KVGhpcyBmZWF0dXJlIHdhcyBhdCBsZWFzdCByZXF1ZXN0ZWQgYnkgNCBvciA1IGRp ZmZlcmVudCBwZW9wbGUsIHRvIG5vIGF2YWlsLg0KDQp5b3UgbWlnaHQgQ0MgeW91cnNlbGYgdG8g dGhlIGJ1Z3JlcG9ydChSRkUpIGFuZCB2b3RlIG9uIGl0LCBtYXliZQ0KdGhpcyB3YXkgaXQgd2ls bCBnZXQgc29tZSB0cmFjdGlvbi4NCg0Ka2luZCByZWdhcmRzDQoNClN2ZW4NCg0KDQoNCl9fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpVc2VycyBtYWlsaW5n IGxpc3QNClVzZXJzQG92aXJ0Lm9yZzxtYWlsdG86VXNlcnNAb3ZpcnQub3JnPg0KaHR0cDovL2xp c3RzLm92aXJ0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3VzZXJzDQoNCg== --_000_1460209771158938camelacroniscom_ Content-Type: text/html; charset="utf-8" Content-ID: <F5ABFF81E4739C40A0F5CFF6BEAA66D3@acronis.com> Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdj5JJ2QgbGlr ZSB0byBzZWUgdGhlIGF1dG9zdGFydCBmZWF0dXJlIGFzIHdlbGwuIEluIG15IGNhc2UgSSBuZWVk IHRvIGF1dG9zdGFydCBhIHZpcnR1YWwgcm91dGVyIFZNIGF0IHJlbW90ZSBzaXRlLiBUaGUgaXNz dWUgaXMgdGhhdCBvVmlydCBjYW4ndCBzZWUgdGhlIHJlbW90ZSBob3N0IHVudGlsIHRoZSB2aXJ0 dWFsIHJvdXRlciBpcyBzdGFydGVkIG9uIHRoaXMgaG9zdC4gU28gSEEgaXMgbm90IGFuIG9wdGlv bi48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pk9uIFNhdCwgMjAxNi0wNC0wOSBhdCAw ODo1MCAmIzQzOzAyMDAsIFN2ZW4gS2llc2tlIHdyb3RlOjwvZGl2Pg0KPGJsb2NrcXVvdGUgdHlw ZT0iY2l0ZSI+DQo8cHJlPk9uIDA2LjA0LjIwMTYgMDc6NDYsIEJyZXR0IEkuIEhvbGNvbWIgd3Jv dGU6DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIj4NCkluIFZNd2FyZSB3ZSBjb3VsZCBzZXR1cCBn dWVzdHMgdG8gYXV0b3N0YXJ0IHdoZW4gdGhlIGhvc3Qgc3RhcnRlZCBhbmQNCmRlZmluZSB0aGUg b3JkZXIuICBJcyB0aGF0IGRvYWJsZSBpbiBvVmlydD8gIFRoZSBvbmx5IHRoaW5nIEkndmUgc2Vl bg0KaXMgdGhlIHdhdGNoZG9nIGFuZCB0ZWxsIGl0IHRvIHJlc2V0IGJ1dCBub3RoaW5nIHRoYXQg YWxsb3dzIG1lIHRvDQpkZWZpbmUgd2hvIHN0YXJ0cyB1cCB3aGVuIGFuZCBpZiB0aGV5IGF1dG9z dGFydC4gIEkgYXNzdW1lIGl0J3MgdGhlcmUNCmJ1dCBJIG11c3QgYmUgbWlzc2luZyBpdCBvciBo YXZlbid0IGZvdW5kIGl0IGluIHRoZSB3ZWIgcG9ydGFsLg0KPC9ibG9ja3F1b3RlPg0KDQpTZWUg dGhpcyBsb25nIHN0YW5kaW5nIGJ1ZzoNCg0KPGEgaHJlZj0iaHR0cHM6Ly9idWd6aWxsYS5yZWRo YXQuY29tL3Nob3dfYnVnLmNnaT9pZD0xMTY2NjU3Ij5odHRwczovL2J1Z3ppbGxhLnJlZGhhdC5j b20vc2hvd19idWcuY2dpP2lkPTExNjY2NTc8L2E+DQoNCmFsc28gc2VhcmNoaW5nIHRoaXMgTUwg Zm9yICZxdW90O2F1dG9zdGFydCZxdW90OyBhbmQgJnF1b3Q7Vk0mcXVvdDsNCg0KdHVybnMgdXAg dGhpcyBzYW1lIGRpc2N1c3Npb24gZXZlcnkgZmV3IG1vbnRocy4NCg0Kc2FkbHkgbm8gZGV2IHNl ZW1zIHRvIGdyYXNwIHRoZSBpbXBvcnRhbmNlIG9mIHRoaXMgZmVhdHVyZSwgc28gaXQncw0KYWx3 YXlzIHJhdGlvbmFsc2VkIHRoYXQgaXQncyBub3QgbmVlZGVkIG9yIHRoZSBIQSBmZWF0dXJlIGlz IGVub3VnaCAoaXQNCmlzbid0KS4NCg0KSSBkb24ndCBrbm93IHdoeSB0aGUgYWxyZWFkeSBpbXBs ZW1lbnRlZCBsaWJ2aXJ0IGF1dG9zdGFydCBmZWF0dXJlDQpkb2VzIG5vdCBnZXQgc2ltcGx5IHBh c3NlZCB0aHJvdWdoLg0KDQpUaGlzIGZlYXR1cmUgd2FzIGF0IGxlYXN0IHJlcXVlc3RlZCBieSA0 IG9yIDUgZGlmZmVyZW50IHBlb3BsZSwgdG8gbm8gYXZhaWwuDQoNCnlvdSBtaWdodCBDQyB5b3Vy c2VsZiB0byB0aGUgYnVncmVwb3J0KFJGRSkgYW5kIHZvdGUgb24gaXQsIG1heWJlDQp0aGlzIHdh eSBpdCB3aWxsIGdldCBzb21lIHRyYWN0aW9uLg0KDQpraW5kIHJlZ2FyZHMNCg0KU3Zlbg0KDQo8 L3ByZT4NCjxwcmU+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18NClVzZXJzIG1haWxpbmcgbGlzdA0KPGEgaHJlZj0ibWFpbHRvOlVzZXJzQG92aXJ0Lm9yZyI+ VXNlcnNAb3ZpcnQub3JnPC9hPg0KPGEgaHJlZj0iaHR0cDovL2xpc3RzLm92aXJ0Lm9yZy9tYWls bWFuL2xpc3RpbmZvL3VzZXJzIj5odHRwOi8vbGlzdHMub3ZpcnQub3JnL21haWxtYW4vbGlzdGlu Zm8vdXNlcnM8L2E+DQo8L3ByZT4NCjwvYmxvY2txdW90ZT4NCjwvYm9keT4NCjwvaHRtbD4NCg== --_000_1460209771158938camelacroniscom_--
participants (8)
-
Adam Litke -
Brett I. Holcomb -
Joop -
Martin Sivak -
Michael Kleinpaste -
Nir Soffer -
Pavel Gashev -
Sven Kieske