Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

updating release doc to remove linux kernel2 #9482

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

updating release doc to remove linux kernel2 #9482

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
102 changes: 29 additions & 73 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,6 @@ new packages coming in and invalidating your efforts.
For each platform
([darwin](https://packages.chef.io/files/staging/habitat/latest/hab-x86_64-darwin.zip),
[linux](https://packages.chef.io/files/staging/habitat/latest/hab-x86_64-linux.tar.gz),
[linux-kernel2](https://packages.chef.io/files/staging/habitat/latest/hab-x86_64-linux-kernel2.tar.gz),
[windows](https://packages.chef.io/files/staging/habitat/latest/hab-x86_64-windows.zip)),
download the latest release candidate CLI from `packages.chef.io`. You
**must** have run the `/expeditor` Slack command above _before_
Expand All @@ -53,21 +52,6 @@ curl https://raw.githubusercontent.com/habitat-sh/habitat/master/components/hab/
sudo hab pkg install core/hab --binlink --force --channel=staging
```

#### Linux, Kernel 2

Run either of the following commands:

``` sh
curl https://raw.githubusercontent.com/habitat-sh/habitat/master/components/hab/install.sh \
| sudo bash -s -- -c staging -t x86_64-linux-kernel2
```
(Note the addition of the target option on the "curlbash" command! Without this you will end up with
the modern Linux version, and things won't work properly!)

```sh
sudo hab pkg install core/hab --binlink --force --channel=staging
```

#### macOS

``` sh
Expand Down Expand Up @@ -120,7 +104,9 @@ Here is how you can validate the version of the cli, supervisor and the supervis
On Linux:
``` sh
hab --version
hab sup --version
sudo -E hab sup --version

hab studio rm
hab studio enter
hab --version
sup-log
Expand All @@ -133,6 +119,7 @@ On Windows:
``` pwsh
hab --version
hab sup --version
hab studio rm
hab studio enter
hab --version
Get-Supervisorlog
Expand All @@ -158,81 +145,50 @@ hab studio enter
```
Then, once inside the Studio, you could try these:

On Linux:

``` sh
# Does the version of the cli inside the studio match staging?
hab --version
# Does the version of the supervisor inside the studio match staging?
sup-log
^C
# build the apache plan
build core-plans/httpd
# build the redis plan
build core-plans/redis
source results/last_build.env
hab svc load $pkg_ident
sup-log
# Is Apache running
# Is redis running and accepting connections
^C
# Is it connectable?
hab pkg exec $pkg_ident redis-cli --stat
```

On Windows:
``` sh
# Does the version of the cli inside the studio match staging?
hab --version
# Does the version of the supervisor inside the studio match staging?
# The supervisor log will come up in a different window in a non-docker
# Windows Studio. Make sure to "accept" any windows firewall requests.
Get-SupervisorLog
# build the nginx plan
build core-plans/nginx
. results/last_build.ps1
hab svc load $pkg_ident
# Look at the log window to see if nginx running
# Is it responding?
hab pkg exec core/busybox-static wget http://localhost -S
Invoke-WebRequest http://localhost
```

On Linux, testing the Docker studio is identical, except you enter
Testing the Docker studio is identical, except you enter
using the following command instead:

```sh
hab studio enter -D
```

Test both in the chroot and docker studios on x86 linux.

### Validating x86_64-linux-kernel2

For this PackageTarget it is important that you perform validation on a Linux system running a 2.6 series kernel. CentOS 6 is recommended because it ships with a kernel of the appropriate age, but any distro with a Kernel between 2.6.32 and 3.0.0 can be used. Included in the `support/validation/x86_64-linux-kernel2` directory in this repository is a Vagrantfile that will create a CentOS-6 VM to perform the validation. You can also run a VM in EC2.

The Vagrantfile is configured to grab the
[core-plans](https://github.com/habitat-sh/core-plans) repository (to
give you something to build), as well as grab the secret key for your
`HAB_ORIGIN` (using the `HAB_ORIGIN` and `HAB_AUTH_TOKEN` variables in
your environment). Additionally, it will automatically install the
release candidate `hab` binary from the `staging` channel unless you
explicitly override that with the `INSTALL_CHANNEL` variable (see below).


```sh
export HAB_ORIGIN=...
export HAB_AUTH_TOKEN=...

# Only if you *don't* want the staging artifact, for some reason
export INSTALL_CHANNEL=...

vagrant up
vagrant ssh
```
Once inside the VM, set your override environment variables (as above)
and experiment. For example:

```sh
export HAB_INTERNAL_BLDR_CHANNEL=staging
export HAB_STUDIO_SECRET_HAB_INTERNAL_BLDR_CHANNEL=staging
export HAB_ORIGIN=<my_origin>
hab studio enter
```

Then, once inside the Studio, you could try these:

``` sh
# Does the version of the cli inside the studio match staging?
hab --version
# Does the version of the supervisor inside the studio match staging?
sup-log
^C
# build the apache plan
build core-plans/redis
source results/last_build.env
hab svc load $pkg_ident
sup-log
# Is Redis running and reporting "Ready to accept connections"
^C
```
Test both in the native and docker studios on x86 linux and windows.

## Promote from Staging to Current

Expand Down
35 changes: 0 additions & 35 deletions support/validation/x86_64-linux-kernel2/Vagrantfile
View file
Open in desktop

This file was deleted.

Loading