The ansible instance is set up using ansible. The nginx credentials
were missing which let the sync of the sstate-cache mirror fail.
Thus, adapting the environment by adding the credentials.
Including the update of the documentation
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
On the ansible instance we saw that the seed job concept was working.
To be as felxible as possible as well on the HAC instance this
concept shall be integrated into this instance. Therefore this commit
holds all the steps so that the yocto build pipeline is starting to
build.
NOTE: currently the NWL project is in progress and the build is not
succeeding.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
to have the ssh key of nginx available in the docker instance, the
manage script needed to be adapted as each key was added with a
single mount command.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
There are different kubernetes tools. This commit holds a table with a
comparisson of the different tools.
Additionally a K3s instance was set up and documented.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
the plugin versions are as important as the jenkins version.
One could update the plugins via Jenkins UI and with that you
might loose the control of versions in case of a rebuilt for an
already released software. Thus, this section was added and we
need to integrate the versions as well.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
With this commit the investigations regarding running a playbook
on specific host(s) are documented.
There are different host selection possibilities like limitation,
providing an inventory with only one host (command line), using
the playbook keyword 'when' or by providing a variable for the
playbook keyword 'hosts'.
This part is important if it comes to an ochestration of hosts
with different running and setup states.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
To use the GitLab CI on a project, a server needs to install a
runner. The NetModule Know-How documentation holds already an
instruction guide about how to set up such a runner. For
completness a short summary is added to the next-level CI page.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
there is a need of standardization and flexibility for project
specific parts. Thus, a new section is added where the ansible
work shows how to bring that into a standardized workflow.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
added the hint that we use the already available declarative
pipeline of NWL which is running on the HAC instance.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
This commit holds now all the documentation to bring up a jenkins
instance using ansible and AWX.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
The topic Jcasc was already handled. With this commit we are able to
setup a Jenkins by using docker-compose.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
With this commit we set up a machine until building a docker image on
it. The next step would be to start the docker container or the
docker compound.
It is as well possible to run the playbooks without having an AWX
instance but AWX gives you more overview about the things that are
available and happening. E.g. you can set up schedules for re-
occurring jobs. For reasons of completness an example to launch
a playbook from command line is added in the conclusion section.
Additionally I added a section about combining playbooks in one
common playbook which might be useful to have really a single
button press for setting up a new machine.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
AWX uses separate ssh keys to access the host. The host itself uses
its own ssh keys to access bitbucket. The added section shows a way
how to handle such a condition.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
the topic about using the Git server (Bitbucket or GitLab) for
user-space applications has driven me into that direction.
Unfortunately there is a lack of information and permission to
move on with this topic. Thus, I postponed it until I get some
news :-)
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
Documented the job template to get the information residing in
the playbook getting_started/os-rls.yml
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
this commit holds the information about how to synchronize a git
project containing ansible playbooks and hosts with AWX.
NOTE: getting the hosts of the inventroy file is not that obvious,
hence it is worth to read it.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
The latest version of AWX requires a Kubernetes Cluster. This
commit holds the update of the page and shows both installation
methodes (directly with docker and the latest version with a
minikube).
Additionally, I added a new section setting up a virtual machine
for test purpose. With it another section for accessing such
machines over SSH.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
Documented the setup of an AWX instance using docker-compose.
Added a first playbook including inventory
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
the nightly timer triggers the job without target parameter. Thus,
the job checks if it is a nightly build and takes a default target
which is the clearfog one.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>