jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
Since we're now offering regular updates for Atomic Workstation, it's time for a detailed blog post about installing it and running it. Maybe even a series.
Ideal would be a summary article in Fedora Magazine, and a detailed series over time on the Atomic blog.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/375
davdunc reported a new issue against the project: `atomic-wg` that you are following:
``
blog post announcing the availability of F27 Atomic in the AWS Marketplace.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/366
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
This ticket will be used throughout the f27 release to track potential blocker bugs and/or important bugs for the next release. A blocker bug is a bug that we will choose not to release on if it is not fixed. An important bug is a bug that we want fixed but may choose not to block on.
**Blocker Bugs**
- [BZ#1490505](https://bugzilla.redhat.com/show_bug.cgi?id=1490505) cloud-init fails when calling `xfs_growfs /dev/mapper/atomicos-root` on Fedora Atomic Host
**Important Bugs**
Over time only the description of this bug will be edited for updates. The comments of this bug will be used like a *changelog* for the description.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/331
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
We need an article on how to migrate from built-in kubernetes to system container kubernetes when migrating from F26 to F27. This is our most critical article for the release.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/355
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
We've had a few discussions about including `cri-o` in atomic host and one [recently](https://pagure.io/atomic-wg/issue/407) discussing both `cri-o` and `podman`. The consensus on `cri-o` was that if someone needs to get openshift/kubernetes then it's not that much harder to also get `cri-o` as part of the same process (for example, using the `openshift-ansible` installer).
`podman`, however, is something we could consider adding because it gives us a nice familiar CLI with possibly less bloat. `podman` is brand new and there is still some work to be done on it. It was decided that we should evaluate adding `podman` into atomic host in a few months time. This was proposed at the [feb 7th WG meeting](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-February/msg00024.html).
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422
miabbott reported a new issue against the project: `atomic-wg` that you are following:
``
We've received requests/complaints from #atomic on Freenode about the lack of up to date documentation for composing custom ostrees.
```
I've been trying to build my own atomic repo using rpm-ostree for the past couple days.
I'm using a Fedora 27 workstation to build a repo for Atomic Fedora 27.
I've tried adapting multiple instructions found online (most of them very old).
Do working instructions exist anywhere for Fedora 27 Atomic?
```
It seems like we could benefit from an updated version of @jasonbrooks blog post for Fedora 27:
https://www.projectatomic.io/blog/2014/11/build-your-own-atomic-updates/
And perhaps another edition that covers composing your own F27 Workstation ostree?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/386
sanja reported a new issue against the project: `atomic-wg` that you are following:
``
**Goal: cleanup** by archiving the repositories in this list. Thanks @smilner for the initial list.
Please add repositories you think should be archived or comment which ones should not be archived from this list.
* ansible-role-atomic-reactor
* ansible-role-osbs-secret
* openshift2nulecule (archived)
* fedora-productimg-atomic
* ansible-role-pulp-secret
* ansible-role-osbs-proxy
* ansible-role-install-openshift
* atomic-enterprise-ansible
* forward-journald
* vagrant-adbinfo
* docker-py
* image-inspector
* ruby-hello-world
* atomic-enterprise
* heat-kubernetes
* docker-fedora-images
* heat-atomic
* oversight
* adb-vagrant-redhat-certification
* anaconda
* rhci-docker
* atomic-enterprise-training
* ansible-osbs
* nulecule (archived)
* commissaire-mvp [should be archived]
* commctl [should be archived]
* commissaire-http [should be archived]
* commissaire (archived)
* commissaire-service [should be archived]
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/428
ttomecek reported a new issue against the project: `atomic-wg` that you are following:
``
Hi, I just tried to build my container image and let osbs generate the `help.1` file. It worked!
The only problem I have is that the present version deployed inside infrastructure does not support rendering tables.
Which means that this help.md page
```
% tools (1) Container Image Pages
% Tomas Tomecek
% September 11th, 2017
# NAME
tools - container with all the management tools you miss in Atomic Host
# DESCRIPTION
You find plenty of well-known tools within this container. Here comes the full list:
| Package | Summary | Executables |
| --------------- | ------------------------------------------------------------------------------------------- | ---------------------------------- |
| bash-completion | Programmable completion for Bash | |
| bc | GNU's bc (a numeric processing language) and dc (a calculator) | /usr/bin/bc |
| | | /usr/bin/dc |
| bind-utils | Utilities for querying DNS name servers | /usr/bin/arpaname |
```
is translated to
```
tools (1) September 11th, 2017 tools (1)
NAME
tools - container with all the management tools you miss in Atomic Host
DESCRIPTION
You find plenty of well-known tools within this container. Here comes the full list:
USAGE
You should invoke this container using atomic command:
$ atomic run f26/tools
```
(yes, the table is missing)
when it should be translated to
```
tools (1) September 11th, 2017 tools (1)
NAME
tools - container with all the management tools you miss in Atomic Host
DESCRIPTION
You find plenty of well-known tools within this container. Here comes the full list:
┌────────────────┬────────────────────────────────────────────┬────────────────────────────────────┐
│Package │ Summary │ Executables │
├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤
│bash-completion │ Programmable completion for Bash │ │
├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤
│bc │ GNU's bc (a numeric processing language) │ /usr/bin/bc │
│ │ and dc (a calculator) │ │
├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤
│ │ │ /usr/bin/dc │
├────────────────┼────────────────────────────────────────────┼────────────────────────────────────┤
│bind-utils │ Utilities for querying DNS name servers │ /usr/bin/arpaname │
```
I used `golang-github-cpuguy83-go-md2man-1.0.7-1.fc28.x86_64` to do that. Would be awesome to have that version deployed.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/374
sanja reported a new issue against the project: `atomic-wg` that you are following:
``
**Problem**
We are confusing newcomers through redundant/unused resources that are mentioned in various places - we need to clean up and make the start more welcoming.
**Actions**
* delete/archive/rename redundant resources
**Goals**
* community growth - both users and contributors
* new healthy and active baseline to operate from
---
**Proposed Changes**
Please express your opinions in the comments. If you have no comments, just vote with a "+1".
***Mailing Lists***
* delete the two unused mailing lists (delete atomic-announce and atomic, keep just atomic-devel(a)projectatomic.io and rename atomic-devel to just atomic)
***IRC Channels***
* rename (or delete it not used) #fedora-atomic as people stumble upon it and ask questions there - it's more intuitive to send them to #atomic directly if there is no #fedora-atomic (if #fedora-atomic is being used but it's more for release engineering/build problems, whoever is responsible for it, please rename it so that people who want to contribute/get support for Atomic don't stumble on it)
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/427