Hi All,
Looks like we have a few hosts assigned to the Openstack-Puppet project that have been hanging around for a while. I'd like to add this project to our automatic reaper script.
Any objections? Any hosts that need to stick around while you get data off?
Cheers! Brian
On 14 Oct, Brian Stinson wrote:
Hi All,
Looks like we have a few hosts assigned to the Openstack-Puppet project that have been hanging around for a while. I'd like to add this project to our automatic reaper script.
Hi,
You can return all of them at any time, but before you do that is there a way to see a list of hosts assigned to a user ? I'd like to know how many host we left pending, and in what times, if I have to correct the way we're returning them, and not leaving anything behing. In any case, how is the reaper script working ? checks for ssh logins time ? how much time do we have until hosts are forcefully returned ?
thanks.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi
On 14/10/15 16:08, Gabriele Cerami wrote:
On 14 Oct, Brian Stinson wrote:
Hi All,
Looks like we have a few hosts assigned to the Openstack-Puppet project that have been hanging around for a while. I'd like to add this project to our automatic reaper script.
Hi,
You can return all of them at any time, but before you do that is there a way to see a list of hosts assigned to a user ? I'd like to know how many host we left pending, and in what times, if I have to correct the way we're returning them, and not leaving anything behing. In any case, how is the reaper script working ? checks for ssh logins time ? how much time do we have until hosts are forcefully returned ?
At the moment, its very casual - you get atleast 24 hrs + time of day in date you requested the machine. so if you ask for a node at 00:00 then you get 48 hrs before the machine is recovered.
If you request a machine at 23:59 on a day then you get 24 hrs.
The clock starts from the time of request for node, and the entire session is handled as a single block ( ie. if you ask for 3 nodes, they will all be recovered at the same time ).
I will modify the /Inventory call to allow folks to specify their own api key, and get a host list. Let me confirm once that is done.
In most cases, the hosts get left behind due to a crash or a unclean shutdown in the jenkis job itself.
At some point in the future, once we start getting closer to capacity limits, we want to try and bring the deployed time down to 6 to 8 hrs per host and recover it that way ( but we are a way from hitting those yet ).
regards,
- -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
This sounds good, please do.
If any of our tests are running for 24 hours, there's certainly something wrong, and we should notice from Jenkins if nothing else.
Ben
On Wed, Oct 14, 2015 at 8:15 AM, Karanbir Singh kbsingh@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi
On 14/10/15 16:08, Gabriele Cerami wrote:
On 14 Oct, Brian Stinson wrote:
Hi All,
Looks like we have a few hosts assigned to the Openstack-Puppet project that have been hanging around for a while. I'd like to add this project to our automatic reaper script.
Hi,
You can return all of them at any time, but before you do that is there a way to see a list of hosts assigned to a user ? I'd like to know how many host we left pending, and in what times, if I have to correct the way we're returning them, and not leaving anything behing. In any case, how is the reaper script working ? checks for ssh logins time ? how much time do we have until hosts are forcefully returned ?
At the moment, its very casual - you get atleast 24 hrs + time of day in date you requested the machine. so if you ask for a node at 00:00 then you get 48 hrs before the machine is recovered.
If you request a machine at 23:59 on a day then you get 24 hrs.
The clock starts from the time of request for node, and the entire session is handled as a single block ( ie. if you ask for 3 nodes, they will all be recovered at the same time ).
I will modify the /Inventory call to allow folks to specify their own api key, and get a host list. Let me confirm once that is done.
In most cases, the hosts get left behind due to a crash or a unclean shutdown in the jenkis job itself.
At some point in the future, once we start getting closer to capacity limits, we want to try and bring the deployed time down to 6 to 8 hrs per host and recover it that way ( but we are a way from hitting those yet ).
regards,
Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJWHnGmAAoJEI3Oi2Mx7xbtkeoH/RT1gcZ9tM9vk9Pzb6w+3RQ5 df3SX+LwEQ5fO9Vzb2NQBWJjsL7zzz5PdSBkXO7y7o1DUY7rXnks4l85D5dlQXZu 0s5QddNnzom7fvpcInoVQW6fyExNCVfUdJc+7q/Icv0JEDToNa1YbjJLkISEjDWD k+XrX4V++inKBNIakhRHCos+OVhiUJLhbQPtKY2tJ7sDzdpdIsm+ShuQIXsYUSOZ 3bifcN7+WSyhxWPEHXrkpt9vFfF2g31EprLETPjtzwV4a17ysS1spIhgt5pu+kWz gW5QEQUXq6lMRISHj0CeJJt7OEuQpiEqzQB/DwDv4pM1Zt8wduuqSsC083SLt5c= =UYRv -----END PGP SIGNATURE----- _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-
Ben Kero -
Brian Stinson -
Gabriele Cerami -
Karanbir Singh