I believe there is a fair chunk of developers that are familiar with the
katello-deploy repository [1]. The repository started to house our bats
tests inspired by foreman-bats and has grown to represent a set of tools,
tasks and functionality for developers. To date, it can do things like:
Spin up Foreman nightly and 1.11 via Vagrant
Spin up Katello nightly and 3.0 via Vagrant
Spin up a development environment that follows common practices and
configurations
Run installations with koji scratch builds
Run installations pointed at puppet module PRs
Install from koji-repos
Docker containers for some common tasks
Katello client containers for registration/package install testing
Jenkins Job Builder environment runtime
Redmine container for testing updates (still in PR phase)
When we switched the installer over to scenarios, we moved katello-deploy
to be more Foreman centric with respect to being able to spin up Foreman
directly (and not just Katello+Foreman).
I would like to propose moving katello-deploy from its current state and
home to be centered in the community as a suite of development tools and
runtime environments. The goal being to not only allow developers to be
more efficient when they need a particular environment for development or
testing but as an entry point to lower the barrier for users as well.
If this sounds like something the community would want and benefit from
then I would like to:
a) identify any changes that should be made before centralizing it (e.g.
changing the repo name and ownership)
b) tackle any code related issues identified from this discussion
c) gather a list of personal developer repositories for development tasks
and tooling and triage them for inclusion in this repo with their permission
> All,
>
> I believe there is a fair chunk of developers that are familiar with the
> katello-deploy repository [1]. The repository started to house our bats
> tests inspired by foreman-bats and has grown to represent a set of tools,
> tasks and functionality for developers. To date, it can do things like:
>
> * Spin up Foreman nightly and 1.11 via Vagrant
> * Spin up Katello nightly and 3.0 via Vagrant
> * Spin up a development environment that follows common practices and
> configurations
> * Run installations with koji scratch builds
> * Run installations pointed at puppet module PRs
> * Install from koji-repos
> * Docker containers for some common tasks
> - Katello client containers for registration/package install testing
> - Jenkins Job Builder environment runtime
> - Redmine container for testing updates (still in PR phase)
>
> When we switched the installer over to scenarios, we moved katello-deploy
> to be more Foreman centric with respect to being able to spin up Foreman
> directly (and not just Katello+Foreman).
>
>
> I would like to propose moving katello-deploy from its current state and
> home to be centered in the community as a suite of development tools and
> runtime environments. The goal being to not only allow developers to be
> more efficient when they need a particular environment for development or
> testing but as an entry point to lower the barrier for users as well.
>
> If this sounds like something the community would want and benefit from
> then I would like to:
>
> a) identify any changes that should be made before centralizing it (e.g.
> changing the repo name and ownership)
> b) tackle any code related issues identified from this discussion
> c) gather a list of personal developer repositories for development tasks
> and tooling and triage them for inclusion in this repo with their permission
>
>
>
+1 in general, its getting harder and harder to reproduce full setup (e.g.
katello, discovery, openscap, remote execution etc).
we already see multiple vagrant setup [2] / docker environments [3] which
imho could be located in one place for everyone to consume…
further, it would be probably be used a learning vm for both new users and
those who want to write plugins, either based on develop or on stable
releases.
> All,
>
> I believe there is a fair chunk of developers that are familiar with the
> katello-deploy repository [1]. The repository started to house our bats
> tests inspired by foreman-bats and has grown to represent a set of
> tools, tasks and functionality for developers. To date, it can do things
> like:
>
> * Spin up Foreman nightly and 1.11 via Vagrant
> * Spin up Katello nightly and 3.0 via Vagrant
> * Spin up a development environment that follows common practices and
> configurations
> * Run installations with koji scratch builds
> * Run installations pointed at puppet module PRs
> * Install from koji-repos
> * Docker containers for some common tasks
> - Katello client containers for registration/package install testing
> - Jenkins Job Builder environment runtime
> - Redmine container for testing updates (still in PR phase)
>
> When we switched the installer over to scenarios, we moved
> katello-deploy to be more Foreman centric with respect to being able to
> spin up Foreman directly (and not just Katello+Foreman).
>
>
> I would like to propose moving katello-deploy from its current state and
> home to be centered in the community as a suite of development tools and
> runtime environments. The goal being to not only allow developers to be
> more efficient when they need a particular environment for development
> or testing but as an entry point to lower the barrier for users as well.
katello-deploy has proved to be very helpful. +1 for making it an
official tool for test/devel setups of the Foreman.
···
On 03/23/2016 11:14 PM, Eric D Helms wrote:
If this sounds like something the community would want and benefit from
then I would like to:
a) identify any changes that should be made before centralizing it
(e.g. changing the repo name and ownership)
b) tackle any code related issues identified from this discussion
c) gather a list of personal developer repositories for development
tasks and tooling and triage them for inclusion in this repo with their
permission
It'd be great to see something akin to community-templates for setup -
different setup styles (packages, source, with/without plugins), on
different platforms (want to run a testbed on EC2? here you go!).
It took time to get traction in community-templates, but now we see
significant input in maintaining all the different template types -
hopefully this will got the same way. Definitely a candidate for a
deep-dive / blog post once the first cut is ready
To move this away from being Katello centric, the first thing would be, I
assume, to rename the repository and thus the internals. Suggestions
welcome, throwing out a few ideas:
foreman-deploy
foreman-dev-tools
foreman-dev
foreman-devel
foreman-tools
Forklift
Taisun (strongest crane in existence)
???
Eric
···
On Tue, Mar 29, 2016 at 4:13 AM, Tomas Strachota wrote:
On 03/23/2016 11:14 PM, Eric D Helms wrote:
All,
I believe there is a fair chunk of developers that are familiar with the
katello-deploy repository [1]. The repository started to house our bats
tests inspired by foreman-bats and has grown to represent a set of
tools, tasks and functionality for developers. To date, it can do things
like:
Spin up Foreman nightly and 1.11 via Vagrant
Spin up Katello nightly and 3.0 via Vagrant
Spin up a development environment that follows common practices and
configurations
Run installations with koji scratch builds
Run installations pointed at puppet module PRs
Install from koji-repos
Docker containers for some common tasks
Katello client containers for registration/package install testing
Jenkins Job Builder environment runtime
Redmine container for testing updates (still in PR phase)
When we switched the installer over to scenarios, we moved
katello-deploy to be more Foreman centric with respect to being able to
spin up Foreman directly (and not just Katello+Foreman).
I would like to propose moving katello-deploy from its current state and
home to be centered in the community as a suite of development tools and
runtime environments. The goal being to not only allow developers to be
more efficient when they need a particular environment for development
or testing but as an entry point to lower the barrier for users as well.
katello-deploy has proved to be very helpful. +1 for making it an official
tool for test/devel setups of the Foreman.
If this sounds like something the community would want and benefit from
then I would like to:
a) identify any changes that should be made before centralizing it
(e.g. changing the repo name and ownership)
b) tackle any code related issues identified from this discussion
c) gather a list of personal developer repositories for development
tasks and tooling and triage them for inclusion in this repo with their
permission
Naming things? Next thing we know you'll be asking us to invalidate a
cache!
Forklift sound cool. Taisun most likely is a trademark.
···
On Tue, Apr 5, 2016 at 2:54 PM, Eric D Helms wrote:
To move this away from being Katello centric, the first thing would be, I
assume, to rename the repository and thus the internals. Suggestions
welcome, throwing out a few ideas:
I believe there is a fair chunk of developers that are familiar with the
katello-deploy repository [1]. The repository started to house our bats
tests inspired by foreman-bats and has grown to represent a set of
tools, tasks and functionality for developers. To date, it can do things
like:
Spin up Foreman nightly and 1.11 via Vagrant
Spin up Katello nightly and 3.0 via Vagrant
Spin up a development environment that follows common practices and
configurations
Run installations with koji scratch builds
Run installations pointed at puppet module PRs
Install from koji-repos
Docker containers for some common tasks
Katello client containers for registration/package install testing
Jenkins Job Builder environment runtime
Redmine container for testing updates (still in PR phase)
When we switched the installer over to scenarios, we moved
katello-deploy to be more Foreman centric with respect to being able to
spin up Foreman directly (and not just Katello+Foreman).
I would like to propose moving katello-deploy from its current state and
home to be centered in the community as a suite of development tools and
runtime environments. The goal being to not only allow developers to be
more efficient when they need a particular environment for development
or testing but as an entry point to lower the barrier for users as well.
katello-deploy has proved to be very helpful. +1 for making it an
official tool for test/devel setups of the Foreman.
If this sounds like something the community would want and benefit from
then I would like to:
a) identify any changes that should be made before centralizing it
(e.g. changing the repo name and ownership)
b) tackle any code related issues identified from this discussion
c) gather a list of personal developer repositories for development
tasks and tooling and triage them for inclusion in this repo with their
permission
> To move this away from being Katello centric, the first thing would be,
> I assume, to rename the repository and thus the internals. Suggestions
> welcome, throwing out a few ideas:
>
> 1) foreman-deploy
> 2) foreman-dev-tools
> 3) foreman-dev
> 4) foreman-devel
> 5) foreman-tools
> 6) Forklift
> 7) Taisun (strongest crane in existence)
> 8) ???
>
On 03/23/2016 11:14 PM, Eric D Helms wrote:
All,
I believe there is a fair chunk of developers that are familiar
with the
katello-deploy repository [1]. The repository started to house
our bats
tests inspired by foreman-bats and has grown to represent a set of
tools, tasks and functionality for developers. To date, it can
do things
like:
* Spin up Foreman nightly and 1.11 via Vagrant
* Spin up Katello nightly and 3.0 via Vagrant
* Spin up a development environment that follows common
practices and
configurations
* Run installations with koji scratch builds
* Run installations pointed at puppet module PRs
* Install from koji-repos
* Docker containers for some common tasks
- Katello client containers for registration/package
install testing
- Jenkins Job Builder environment runtime
- Redmine container for testing updates (still in PR phase)
When we switched the installer over to scenarios, we moved
katello-deploy to be more Foreman centric with respect to being
able to
spin up Foreman directly (and not just Katello+Foreman).
I would like to propose moving katello-deploy from its current
state and
home to be centered in the community as a suite of development
tools and
runtime environments. The goal being to not only allow
developers to be
more efficient when they need a particular environment for
development
or testing but as an entry point to lower the barrier for users
as well.
katello-deploy has proved to be very helpful. +1 for making it an
official tool for test/devel setups of the Foreman.
If this sounds like something the community would want and
benefit from
then I would like to:
a) identify any changes that should be made before
centralizing it
(e.g. changing the repo name and ownership)
b) tackle any code related issues identified from this discussion
c) gather a list of personal developer repositories for
development
tasks and tooling and triage them for inclusion in this repo
with their
permission
[1] https://github.com/Katello/katello-deploy
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from
it, send
an email to foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>
<mailto:foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
>> To move this away from being Katello centric, the first thing would be,
>> I assume, to rename the repository and thus the internals. Suggestions
>> welcome, throwing out a few ideas:
>>
>> 1) foreman-deploy
>> 2) foreman-dev-tools
>> 3) foreman-dev
>> 4) foreman-devel
>> 5) foreman-tools
>> 6) Forklift
>> 7) Taisun (strongest crane in existence)
>> 8) ???
>>
>
> foreman-deploy sounds ok to me.
Ehm, taking back. It might easily get confused with foreman-deployments.
So, forklift would be my second choice.
···
On 04/13/2016 04:55 PM, Tomas Strachota wrote:
> On 04/05/2016 01:54 PM, Eric D Helms wrote:
On 03/23/2016 11:14 PM, Eric D Helms wrote:
All,
I believe there is a fair chunk of developers that are familiar
with the
katello-deploy repository [1]. The repository started to house
our bats
tests inspired by foreman-bats and has grown to represent a
set of
tools, tasks and functionality for developers. To date, it can
do things
like:
* Spin up Foreman nightly and 1.11 via Vagrant
* Spin up Katello nightly and 3.0 via Vagrant
* Spin up a development environment that follows common
practices and
configurations
* Run installations with koji scratch builds
* Run installations pointed at puppet module PRs
* Install from koji-repos
* Docker containers for some common tasks
- Katello client containers for registration/package
install testing
- Jenkins Job Builder environment runtime
- Redmine container for testing updates (still in PR phase)
When we switched the installer over to scenarios, we moved
katello-deploy to be more Foreman centric with respect to being
able to
spin up Foreman directly (and not just Katello+Foreman).
I would like to propose moving katello-deploy from its current
state and
home to be centered in the community as a suite of development
tools and
runtime environments. The goal being to not only allow
developers to be
more efficient when they need a particular environment for
development
or testing but as an entry point to lower the barrier for users
as well.
katello-deploy has proved to be very helpful. +1 for making it an
official tool for test/devel setups of the Foreman.
If this sounds like something the community would want and
benefit from
then I would like to:
a) identify any changes that should be made before
centralizing it
(e.g. changing the repo name and ownership)
b) tackle any code related issues identified from this
discussion
c) gather a list of personal developer repositories for
development
tasks and tooling and triage them for inclusion in this repo
with their
permission
[1] https://github.com/Katello/katello-deploy
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
You received this message because you are subscribed to the
--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
···
On Wed, Apr 13, 2016 at 4:57 PM, Tomas Strachota wrote:
On 04/13/2016 04:55 PM, Tomas Strachota wrote:
On 04/05/2016 01:54 PM, Eric D Helms wrote:
To move this away from being Katello centric, the first thing would be,
I assume, to rename the repository and thus the internals. Suggestions
welcome, throwing out a few ideas:
foreman-deploy
foreman-dev-tools
foreman-dev
foreman-devel
foreman-tools
Forklift
Taisun (strongest crane in existence)
???
foreman-deploy sounds ok to me.
Ehm, taking back. It might easily get confused with foreman-deployments.
So, forklift would be my second choice.
On 03/23/2016 11:14 PM, Eric D Helms wrote:
All,
I believe there is a fair chunk of developers that are familiar
with the
katello-deploy repository [1]. The repository started to house
our bats
tests inspired by foreman-bats and has grown to represent a
set of
tools, tasks and functionality for developers. To date, it can
do things
like:
* Spin up Foreman nightly and 1.11 via Vagrant
* Spin up Katello nightly and 3.0 via Vagrant
* Spin up a development environment that follows common
practices and
configurations
* Run installations with koji scratch builds
* Run installations pointed at puppet module PRs
* Install from koji-repos
* Docker containers for some common tasks
- Katello client containers for registration/package
install testing
- Jenkins Job Builder environment runtime
- Redmine container for testing updates (still in PR phase)
When we switched the installer over to scenarios, we moved
katello-deploy to be more Foreman centric with respect to being
able to
spin up Foreman directly (and not just Katello+Foreman).
I would like to propose moving katello-deploy from its current
state and
home to be centered in the community as a suite of development
tools and
runtime environments. The goal being to not only allow
developers to be
more efficient when they need a particular environment for
development
or testing but as an entry point to lower the barrier for users
as well.
katello-deploy has proved to be very helpful. +1 for making it an
official tool for test/devel setups of the Foreman.
If this sounds like something the community would want and
benefit from
then I would like to:
a) identify any changes that should be made before
centralizing it
(e.g. changing the repo name and ownership)
b) tackle any code related issues identified from this
discussion
c) gather a list of personal developer repositories for
development
tasks and tooling and triage them for inclusion in this repo
with their
permission
[1] https://github.com/Katello/katello-deploy
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
You received this message because you are subscribed to the
--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
To move this away from being Katello centric, the first thing would be,
I assume, to rename the repository and thus the internals. Suggestions
welcome, throwing out a few ideas:
foreman-deploy
foreman-dev-tools
foreman-dev
foreman-devel
foreman-tools
Forklift
Taisun (strongest crane in existence)
???
foreman-deploy sounds ok to me.
Ehm, taking back. It might easily get confused with foreman-deployments.
So, forklift would be my second choice.
On 03/23/2016 11:14 PM, Eric D Helms wrote:
All,
I believe there is a fair chunk of developers that are familiar
with the
katello-deploy repository [1]. The repository started to house
our bats
tests inspired by foreman-bats and has grown to represent a
set of
tools, tasks and functionality for developers. To date, it can
do things
like:
* Spin up Foreman nightly and 1.11 via Vagrant
* Spin up Katello nightly and 3.0 via Vagrant
* Spin up a development environment that follows common
practices and
configurations
* Run installations with koji scratch builds
* Run installations pointed at puppet module PRs
* Install from koji-repos
* Docker containers for some common tasks
- Katello client containers for registration/package
install testing
- Jenkins Job Builder environment runtime
- Redmine container for testing updates (still in PR phase)
When we switched the installer over to scenarios, we moved
katello-deploy to be more Foreman centric with respect to being
able to
spin up Foreman directly (and not just Katello+Foreman).
I would like to propose moving katello-deploy from its current
state and
home to be centered in the community as a suite of development
tools and
runtime environments. The goal being to not only allow
developers to be
more efficient when they need a particular environment for
development
or testing but as an entry point to lower the barrier for users
as well.
katello-deploy has proved to be very helpful. +1 for making it an
official tool for test/devel setups of the Foreman.
If this sounds like something the community would want and
benefit from
then I would like to:
a) identify any changes that should be made before
centralizing it
(e.g. changing the repo name and ownership)
b) tackle any code related issues identified from this
discussion
c) gather a list of personal developer repositories for
development
tasks and tooling and triage them for inclusion in this repo
with their
permission
[1] https://github.com/Katello/katello-deploy
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
You received this message because you are subscribed to the
--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
To move this away from being Katello centric, the first thing would be,
I assume, to rename the repository and thus the internals. Suggestions
welcome, throwing out a few ideas:
foreman-deploy
foreman-dev-tools
foreman-dev
foreman-devel
foreman-tools
Forklift
Taisun (strongest crane in existence)
???
foreman-deploy sounds ok to me.
Ehm, taking back. It might easily get confused with foreman-deployments.
So, forklift would be my second choice.
On 03/23/2016 11:14 PM, Eric D Helms wrote:
All,
I believe there is a fair chunk of developers that are familiar
with the
katello-deploy repository [1]. The repository started to house
our bats
tests inspired by foreman-bats and has grown to represent a
set of
tools, tasks and functionality for developers. To date, it can
do things
like:
* Spin up Foreman nightly and 1.11 via Vagrant
* Spin up Katello nightly and 3.0 via Vagrant
* Spin up a development environment that follows common
practices and
configurations
* Run installations with koji scratch builds
* Run installations pointed at puppet module PRs
* Install from koji-repos
* Docker containers for some common tasks
- Katello client containers for registration/package
install testing
- Jenkins Job Builder environment runtime
- Redmine container for testing updates (still in PR
phase)
When we switched the installer over to scenarios, we moved
katello-deploy to be more Foreman centric with respect to being
able to
spin up Foreman directly (and not just Katello+Foreman).
I would like to propose moving katello-deploy from its current
state and
home to be centered in the community as a suite of development
tools and
runtime environments. The goal being to not only allow
developers to be
more efficient when they need a particular environment for
development
or testing but as an entry point to lower the barrier for users
as well.
katello-deploy has proved to be very helpful. +1 for making it an
official tool for test/devel setups of the Foreman.
If this sounds like something the community would want and
benefit from
then I would like to:
a) identify any changes that should be made before
centralizing it
(e.g. changing the repo name and ownership)
b) tackle any code related issues identified from this
discussion
c) gather a list of personal developer repositories for
development
tasks and tooling and triage them for inclusion in this repo
with their
permission
[1] https://github.com/Katello/katello-deploy
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
You received this message because you are subscribed to the
--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
Thank you all for the input and votes! The winner appears to be Forklift
and thus I will begin (contributions welcome as well) to rename the
libraries within to reflect this name change and clean up a few bits and
pieces before requesting moving to theforeman organization.
Eric
···
On Thu, May 12, 2016 at 3:36 PM, Eric D Helms wrote:
Coming back around to this, the suggestions I saw were narrowed down to:
Forklift
foreman-deploy
foremanize
oh-my-foreman
I created a doodle to capture votes easier, I am not sure if the name
field is actually required but it can be anonymous if does:
To move this away from being Katello centric, the first thing would
be,
I assume, to rename the repository and thus the internals. Suggestions
welcome, throwing out a few ideas:
foreman-deploy
foreman-dev-tools
foreman-dev
foreman-devel
foreman-tools
Forklift
Taisun (strongest crane in existence)
???
foreman-deploy sounds ok to me.
Ehm, taking back. It might easily get confused with foreman-deployments.
So, forklift would be my second choice.
On 03/23/2016 11:14 PM, Eric D Helms wrote:
All,
I believe there is a fair chunk of developers that are
familiar
with the
katello-deploy repository [1]. The repository started to house
our bats
tests inspired by foreman-bats and has grown to represent a
set of
tools, tasks and functionality for developers. To date, it can
do things
like:
* Spin up Foreman nightly and 1.11 via Vagrant
* Spin up Katello nightly and 3.0 via Vagrant
* Spin up a development environment that follows common
practices and
configurations
* Run installations with koji scratch builds
* Run installations pointed at puppet module PRs
* Install from koji-repos
* Docker containers for some common tasks
- Katello client containers for registration/package
install testing
- Jenkins Job Builder environment runtime
- Redmine container for testing updates (still in PR
phase)
When we switched the installer over to scenarios, we moved
katello-deploy to be more Foreman centric with respect to
being
able to
spin up Foreman directly (and not just Katello+Foreman).
I would like to propose moving katello-deploy from its current
state and
home to be centered in the community as a suite of development
tools and
runtime environments. The goal being to not only allow
developers to be
more efficient when they need a particular environment for
development
or testing but as an entry point to lower the barrier for
users
as well.
katello-deploy has proved to be very helpful. +1 for making it an
official tool for test/devel setups of the Foreman.
If this sounds like something the community would want and
benefit from
then I would like to:
a) identify any changes that should be made before
centralizing it
(e.g. changing the repo name and ownership)
b) tackle any code related issues identified from this
discussion
c) gather a list of personal developer repositories for
development
tasks and tooling and triage them for inclusion in this repo
with their
permission
[1] https://github.com/Katello/katello-deploy
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
You received this message because you are subscribed to the
--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
The first stage of this has been completed, with the code switching to
forklift. The next two stages would be:
Rename the repository
Transfer to theforeman github organization
I am of the opinion those two should be done at the same time, with 1 week
pre-warning to users and developers to allow for update preparation to
their usage, scripts and automation so that they do it once and not twice.
I'll leave this idea open for comment for a few days and then plan for the
one week cycle.
Eric
···
On Sat, May 21, 2016 at 10:00 AM, Eric D Helms wrote:
Thank you all for the input and votes! The winner appears to be Forklift
and thus I will begin (contributions welcome as well) to rename the
libraries within to reflect this name change and clean up a few bits and
pieces before requesting moving to theforeman organization.
On Thu, Apr 28, 2016 at 7:41 AM, Ivan Necas inecas@redhat.com wrote:
foremanize
On Tue, Apr 26, 2016 at 11:23 PM, Ivan Necas inecas@redhat.com wrote:
+1 for foreman-deploy.
oh-my-foreman
– Ivan
On Wed, Apr 13, 2016 at 4:57 PM, Tomas Strachota <tstrachota@redhat.com >>>> > wrote:
On 04/13/2016 04:55 PM, Tomas Strachota wrote:
On 04/05/2016 01:54 PM, Eric D Helms wrote:
To move this away from being Katello centric, the first thing would
be,
I assume, to rename the repository and thus the internals.
Suggestions
welcome, throwing out a few ideas:
foreman-deploy
foreman-dev-tools
foreman-dev
foreman-devel
foreman-tools
Forklift
Taisun (strongest crane in existence)
???
foreman-deploy sounds ok to me.
Ehm, taking back. It might easily get confused with
foreman-deployments.
So, forklift would be my second choice.
On 03/23/2016 11:14 PM, Eric D Helms wrote:
All,
I believe there is a fair chunk of developers that are
familiar
with the
katello-deploy repository [1]. The repository started to
house
our bats
tests inspired by foreman-bats and has grown to represent a
set of
tools, tasks and functionality for developers. To date, it
can
do things
like:
* Spin up Foreman nightly and 1.11 via Vagrant
* Spin up Katello nightly and 3.0 via Vagrant
* Spin up a development environment that follows common
practices and
configurations
* Run installations with koji scratch builds
* Run installations pointed at puppet module PRs
* Install from koji-repos
* Docker containers for some common tasks
- Katello client containers for registration/package
install testing
- Jenkins Job Builder environment runtime
- Redmine container for testing updates (still in PR
phase)
When we switched the installer over to scenarios, we moved
katello-deploy to be more Foreman centric with respect to
being
able to
spin up Foreman directly (and not just Katello+Foreman).
I would like to propose moving katello-deploy from its
current
state and
home to be centered in the community as a suite of
development
tools and
runtime environments. The goal being to not only allow
developers to be
more efficient when they need a particular environment for
development
or testing but as an entry point to lower the barrier for
users
as well.
katello-deploy has proved to be very helpful. +1 for making it an
official tool for test/devel setups of the Foreman.
If this sounds like something the community would want and
benefit from
then I would like to:
a) identify any changes that should be made before
centralizing it
(e.g. changing the repo name and ownership)
b) tackle any code related issues identified from this
discussion
c) gather a list of personal developer repositories for
development
tasks and tooling and triage them for inclusion in this repo
with their
permission
[1] https://github.com/Katello/katello-deploy
--
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
--
You received this message because you are subscribed to the
I believe that Github will redirect, at least on transfer.
···
On Wed, May 25, 2016 at 10:13:34AM -0400, Eric D Helms wrote:
> The first stage of this has been completed, with the code switching to
> forklift. The next two stages would be:
>
> 1) Rename the repository
> 2) Transfer to theforeman github organization
>
> I am of the opinion those two should be done at the same time, with 1 week
> pre-warning to users and developers to allow for update preparation to
> their usage, scripts and automation so that they do it once and not twice.
> I'll leave this idea open for comment for a few days and then plan for the
> one week cycle.
> > The first stage of this has been completed, with the code switching to
> > forklift. The next two stages would be:
> >
> > 1) Rename the repository
> > 2) Transfer to theforeman github organization
> >
> > I am of the opinion those two should be done at the same time, with 1
> week
> > pre-warning to users and developers to allow for update preparation to
> > their usage, scripts and automation so that they do it once and not
> twice.
> > I'll leave this idea open for comment for a few days and then plan for
> the
> > one week cycle.
>
> I believe that Github will redirect, at least on transfer.
>
Nice - in that case I'll bump up the time table.
···
On Wed, May 25, 2016 at 10:14 AM, Ewoud Kohl van Wijngaarden < ewoud@kohlvanwijngaarden.nl> wrote:
> On Wed, May 25, 2016 at 10:13:34AM -0400, Eric D Helms wrote:
The katello-deploy repository has been officially renamed to 'forklift' in
concert with the code updates. The next step is to move this officially
into theforeman organization on Github.
···
On Wed, May 25, 2016 at 11:36 AM, Eric D Helms wrote:
On Wed, May 25, 2016 at 10:13:34AM -0400, Eric D Helms wrote:
The first stage of this has been completed, with the code switching to
forklift. The next two stages would be:
Rename the repository
Transfer to theforeman github organization
I am of the opinion those two should be done at the same time, with 1
week
pre-warning to users and developers to allow for update preparation to
their usage, scripts and automation so that they do it once and not
twice.
I’ll leave this idea open for comment for a few days and then plan for
the
one week cycle.
I believe that Github will redirect, at least on transfer.
In one weeks time, I'd like to officially move Forklift to the Foreman
organization. If there are any objections or concerns, speak now or forever
hold your peace.
The following developers currently have write access and thus I'd like to
request a team setup to ensure we keep access:
···
On Wed, Jun 1, 2016 at 11:01 AM, Eric D Helms wrote:
The katello-deploy repository has been officially renamed to ‘forklift’ in
concert with the code updates. The next step is to move this officially
into theforeman organization on Github.
On Wed, May 25, 2016 at 10:13:34AM -0400, Eric D Helms wrote:
The first stage of this has been completed, with the code switching to
forklift. The next two stages would be:
Rename the repository
Transfer to theforeman github organization
I am of the opinion those two should be done at the same time, with 1
week
pre-warning to users and developers to allow for update preparation to
their usage, scripts and automation so that they do it once and not
twice.
I’ll leave this idea open for comment for a few days and then plan for
the
one week cycle.
I believe that Github will redirect, at least on transfer.
> Reviving this thread.
>
> In one weeks time, I'd like to officially move Forklift to the Foreman
> organization. If there are any objections or concerns, speak now or forever
> hold your peace.
+1000 for moving.
– Ivan
···
>
> The following developers currently have write access and thus I'd like to
> request a team setup to ensure we keep access:
>
> ehelms (admin)
> jlsherrill (admin)
> stbenjam
> ekohl
> johnpmitsch
> bbuckingham
> beav
>
> Thanks,
> Eric
>
> On Wed, Jun 1, 2016 at 11:01 AM, Eric D Helms wrote:
>
>> The katello-deploy repository has been officially renamed to 'forklift' in
>> concert with the code updates. The next step is to move this officially
>> into theforeman organization on Github.
>>
>> On Wed, May 25, 2016 at 11:36 AM, Eric D Helms >> wrote:
>>
>>>
>>>
>>> On Wed, May 25, 2016 at 10:14 AM, Ewoud Kohl van Wijngaarden < >>> ewoud@kohlvanwijngaarden.nl> wrote:
>>>
>>>> On Wed, May 25, 2016 at 10:13:34AM -0400, Eric D Helms wrote:
>>>> > The first stage of this has been completed, with the code switching to
>>>> > forklift. The next two stages would be:
>>>> >
>>>> > 1) Rename the repository
>>>> > 2) Transfer to theforeman github organization
>>>> >
>>>> > I am of the opinion those two should be done at the same time, with 1
>>>> week
>>>> > pre-warning to users and developers to allow for update preparation to
>>>> > their usage, scripts and automation so that they do it once and not
>>>> twice.
>>>> > I'll leave this idea open for comment for a few days and then plan for
>>>> the
>>>> > one week cycle.
>>>>
>>>> I believe that Github will redirect, at least on transfer.
>>>>
>>>
>>> Nice - in that case I'll bump up the time table.
>>>
>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "foreman-dev" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to foreman-dev+unsubscribe@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Eric D. Helms
>>> Red Hat Engineering
>>> Ph.D. Student - North Carolina State University
>>>
>>
>>
>>
>> --
>> Eric D. Helms
>> Red Hat Engineering
>> Ph.D. Student - North Carolina State University
>>
>
>
>
> --
> Eric D. Helms
> Red Hat Engineering
>
> --
> You received this message because you are subscribed to the Google Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
···
On Sun, Jan 22, 2017 at 11:02 PM, Ivan Necas wrote:
> Eric D Helms writes:
>
>> Reviving this thread.
>>
>> In one weeks time, I'd like to officially move Forklift to the Foreman
>> organization. If there are any objections or concerns, speak now or forever
>> hold your peace.
>
> +1000 for moving.
>
> -- Ivan
>
>>
>> The following developers currently have write access and thus I'd like to
>> request a team setup to ensure we keep access:
>>
>> ehelms (admin)
>> jlsherrill (admin)
>> stbenjam
>> ekohl
>> johnpmitsch
>> bbuckingham
>> beav
>>
>> Thanks,
>> Eric
>>
>> On Wed, Jun 1, 2016 at 11:01 AM, Eric D Helms wrote:
>>
>>> The katello-deploy repository has been officially renamed to 'forklift' in
>>> concert with the code updates. The next step is to move this officially
>>> into theforeman organization on Github.
>>>
>>> On Wed, May 25, 2016 at 11:36 AM, Eric D Helms >>> wrote:
>>>
>>>>
>>>>
>>>> On Wed, May 25, 2016 at 10:14 AM, Ewoud Kohl van Wijngaarden < >>>> ewoud@kohlvanwijngaarden.nl> wrote:
>>>>
>>>>> On Wed, May 25, 2016 at 10:13:34AM -0400, Eric D Helms wrote:
>>>>> > The first stage of this has been completed, with the code switching to
>>>>> > forklift. The next two stages would be:
>>>>> >
>>>>> > 1) Rename the repository
>>>>> > 2) Transfer to theforeman github organization
>>>>> >
>>>>> > I am of the opinion those two should be done at the same time, with 1
>>>>> week
>>>>> > pre-warning to users and developers to allow for update preparation to
>>>>> > their usage, scripts and automation so that they do it once and not
>>>>> twice.
>>>>> > I'll leave this idea open for comment for a few days and then plan for
>>>>> the
>>>>> > one week cycle.
>>>>>
>>>>> I believe that Github will redirect, at least on transfer.
>>>>>
>>>>
>>>> Nice - in that case I'll bump up the time table.
>>>>
>>>>
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "foreman-dev" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to foreman-dev+unsubscribe@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Eric D. Helms
>>>> Red Hat Engineering
>>>> Ph.D. Student - North Carolina State University
>>>>
>>>
>>>
>>>
>>> --
>>> Eric D. Helms
>>> Red Hat Engineering
>>> Ph.D. Student - North Carolina State University
>>>
>>
>>
>>
>> --
>> Eric D. Helms
>> Red Hat Engineering
>>
>> --
>> You received this message because you are subscribed to the Google Groups "foreman-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
