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.

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

Update README with requirements #7

Merged
merged 1 commit into from
Mar 15, 2018
Merged

Update README with requirements #7

merged 1 commit into from
Mar 15, 2018

Conversation

chefsalim
Copy link
Contributor

Update README with requirements

Signed-off-by: Salim Alam [email protected]

@chefsalim chefsalim merged commit d3fc023 into master Mar 15, 2018
@chefsalim chefsalim deleted the SA/README branch March 15, 2018 17:23
Copy link

@tashimi tashimi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tenor-205906780

@@ -1,7 +1,27 @@
# On Prem Habitat Builder
# On Premise Habitat Depot

:construction: THIS IS NOT FOR PRODUCTION USE :construction:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would change this to "This is an MVP/Alpha software Release."


:construction: THIS IS NOT FOR PRODUCTION USE :construction:

## Introduction

This repository contains scripts to install Habitat back-end services. These services (referred to as the On-Premise Habitat Depot) allow for the hosting of Habitat packages (and associated artifacts such as keys) by enterprises in-house (behind the firewall). Habitat clients can be pointed to the on-premise depot and allow for development, execution and management without depending on the public Habitat services.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't have to be an enterprise to use this - it's more accurate to describe as an on-prem/privately hosted option available to anyone

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would be careful about the word client here - it's not specific enough, out of context. Perhaps "Habitat clients such as Supervisors and Studios" instead


This repository contains scripts to install Habitat back-end services. These services (referred to as the On-Premise Habitat Depot) allow for the hosting of Habitat packages (and associated artifacts such as keys) by enterprises in-house (behind the firewall). Habitat clients can be pointed to the on-premise depot and allow for development, execution and management without depending on the public Habitat services.

This work is currently a MVP - it is not intended for general production use.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This work is currently an MVP/alpha release. We will be continually improving it over the next few months, and users should be prepared to actively update their installations to benefit from these updates.

* OS should support `systemd` process manager
* Deployment to bare-metal, VM or container image
* 8 GB or more RAM recommended (for single node)
* Significant free disk space (depends on package storage - plan conservatively)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we provide a number here for how much storage a base install of core plans would require, to help estimate?

I would also clarify (depends on package storage, which depends on the size of the applications you are building and storing here - plan conservatively to avoid needing to move to a larger machine)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1.7Gb for the installation itself. Thats just for the packages required to get the depot up and running.

* Significant free disk space (depends on package storage - plan conservatively)
* Services should be deployed single-node - scale out is not yet supported
* Outbound network (HTTPS) connectivity to WAN is required for the _initial_ install
* Inbound network connectivity from LAN (HTTP) for internal access to the Depot
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"is required for internal clients to access the depot"

* Services should be deployed single-node - scale out is not yet supported
* Outbound network (HTTPS) connectivity to WAN is required for the _initial_ install
* Inbound network connectivity from LAN (HTTP) for internal access to the Depot
* OAuth2 authentication provider (Github and Bitbucket verified)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Github, Github Enterprise, and Bitbucket have all been verified - additional providers can be added).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants