[atomic-wg] Issue #228 `clarify policy on atomic host support for older
Fedora "number" releases`
by Dusty Mabe
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
After talking with people from the fedora community and from the atomic WG it has become clear that there is a lot of confusion on our policy for support for N-1 releases of Fedora Atomic Host.
First off some terminology:
**support**: means that we test and release new 2 week releases for this number release (i.e. we currently test/release new two week releases of Fedora 25 Atomic Host).
**N-1**: currently is Fedora 24 Atomic Host
**life support**: means that we still push out OSTree updates for the OSTree that backs this number release, but we don't create new image releases and we don't formally test it.
Currently we have been offering **support** for the current (N) release of Fedora and **life support** for the previous (N-1) release of Fedora. In the future I'd like to formalize our **support** policy and stop providing **life support** for previous releases once it is no longer a current release.
There are a couple of reasons for this:
- The level of effort going into N-1 is very minimal and I wouldn't want someone running that to get a false sense of security from it.
- If N-1 breaks in releng for whatever reason, spending time on N-1 is not a high priority and I'd like to not have to fix it if it breaks.
For F26 I'd like to formally state this policy of **support**ing only the N release. We can also **life support** the N-1 for an agreed upon time period after the N release (30to60 days or something) to allow for transition.
Note: There is also some discussion about making Fedora Atomic a rolling release. That is outside the scope of this ticket.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/228
6 years, 10 months
[atomic-wg] Issue #266: rpmostree_compose Ansible module
by Trishna Guha
trishnag reported a new issue against the project: `atomic-wg` that you are following:
``
As for Ansible module for atomic host we have `atomic_host` and `atomic_image` modules written.
The plan/purpose of this ticket is to have rpm-ostree modules get done for Ansible as well. We can perhaps have all the `rpm-ostree` options as Ansible modules so that we really do not need to execute rpm-ostree commands as part of `shell`/`command` modules in Ansible.
I wrote `rpmostree compose` Ansible module: https://github.com/ansible/ansible/pull/23209.
Can anyone volunteer to review the PR?
Bringing in @dustymabe @jberkus @walters @jlebon here.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/266
6 years, 10 months
[atomic-wg] Issue #252 `Fix rawhide ISO`
by Colin Walters
walters reported a new issue against the project: `atomic-wg` that you are following:
``
https://kojipkgs.fedoraproject.org/compose/rawhide/latest-Fedora-Rawhide/...
```
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/pylorax/ltmpl.py", line 56, in parse
textbuf = template.render(**variables)
File "/usr/lib/python3.6/site-packages/mako/template.py", line 462, in render
return runtime._render(self, self.callable_, args, data)
File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 838, in _render
**_kwargs_for_callable(callable_, data))
File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 873, in _render_context
_exec_template(inherit, lclcontext, args=args, kwargs=kwargs)
File "/usr/lib/python3.6/site-packages/mako/runtime.py", line 899, in _exec_template
callable_(context, *args, **kwargs)
TypeError: render_body() missing 1 required positional argument: 'root'
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/252
6 years, 11 months
[atomic-wg] Issue #181 `Vagrant cannot create synced folder`
by Pagure
jorti reported a new issue against the project: `atomic-wg` that you are following:
``
I just launch an unmodified fedora/25-atomic-host box and I get the error that it cannot create the /vagrant synced dir.
```
$ vagrant up
Bringing machine 'default' up with 'libvirt' provider...
==> default: Creating image (snapshot of base box volume).
==> default: Creating domain with the following settings...
==> default: -- Name: mail-server_default
==> default: -- Domain type: kvm
==> default: -- Cpus: 1
==> default: -- Memory: 512M
==> default: -- Management MAC:
==> default: -- Loader:
==> default: -- Base box: fedora/25-atomic-host
==> default: -- Storage pool: default
==> default: -- Image:
/var/lib/libvirt/images/mail-server_default.img (41G)
==> default: -- Volume Cache: default
==> default: -- Kernel:
==> default: -- Initrd:
==> default: -- Graphics Type: vnc
==> default: -- Graphics Port: 5900
==> default: -- Graphics IP: 127.0.0.1
==> default: -- Graphics Password: Not defined
==> default: -- Video Type: cirrus
==> default: -- Video VRAM: 9216
==> default: -- Keymap: en-us
==> default: -- TPM Path:
==> default: -- INPUT: type=mouse, bus=ps2
==> default: -- Command line :
==> default: Creating shared folders metadata...
==> default: Starting domain.
==> default: Waiting for domain to get an IP address...
==> default: Waiting for SSH to become available...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Configuring and enabling network interfaces...
==> default: Rsyncing folder: /home/juan/Vagrant/mail-server/ => /vagrant
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:
Stderr from the command:
mkdir: cannot create directory ‘/vagrant’: Operation not permitted
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/181
6 years, 11 months
[atomic-wg] Issue #270: Update getfedora.org with Digital Ocean
by Josh Berkus
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
Since we're about to have general availability on DO, we want to change GetFedora.org to reflect that.
1. Change the "Amazon" section on https://getfedora.org/en/atomic/download/ to be "Public Cloud" (see suggested title and text below).
2. Combine the two selector boxes for GP2 and Standard instances into one selector box with an extra column called "Storage" which is either "GP2" or "Standard". Label the button which triggers this box "AWS Cloud"
3. Add a new button called "Digital Ocean", which will trigger a similar selector box to the AWS selector, for DO instances.
Suggested Text:
Public Cloud Images for Amazon EC2 and Digital Ocean
The links below will provide you listings of available Atomic Host instances on two public clouds, Amazon EC2 and Digital Ocean. If you already have an account on these clouds, this will provide you one-click launch of an Atomic Host instance.
@dustymabe @jligon @robyduck
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/270
6 years, 12 months