Environmint
Automation for Oracle
What
- Suite of tools to facilitate automation for Oracle/Java
Who?
Mostly Ops...
I posit that we make the tool's GUI less focused on Oracle experts
Who: 1. Non-Expert
- Tom
- Ops
- Manages environments
- Not a Java/Oracle expert
- Wants to:
- Spin up new envs
- Perform BAU tasks
- Follow best practices
- Doesn't want to:
- Learn Java/Oracle
- Will be the tool's champion
Who: 2. Java/Oracle Expert
- Jed
- Often consulting
- Wants to:
- Tune env - may already have "scripts"
- Trial and error some tweaks
- Doesn't want to:
- Learn a DevOps tool
EnvironMint
- Simple Java/Oracle management for non-experts
- Deploy new envs
- Perform standard maintenance tasks
- Perform customer specific maintenance tasks
- Allow input from experts without needing to rely on them
- Facilitating Oracle and DevOps expertise collaboration
EnvironMint - random ideas
- Install whole suite at once
- Chef Cookbook setup, no installer
- RPM/Debs
- Free trial of unlicensed features
- Suite structure
- Add a process supervisor
- Add a tier 1
- TLS (tier 1 as a terminator)
- Single API root
- http://x.envmint.io/API/{node,mintspec,drift,...}
- Would need to design those endpoints...
- Everything can be automated - ie API for everything
EnvironMint - random ideas
- Inline mgmt within areas, less "admin area"
- Interface
- / - System status (dashboard...)
- Add a status function using mintspec
- Aggregates:
- Mintspec info, Drift info, SC status info
- Links to:
- Drift History: Drift reports
- Compliance: Nodes (mintspec) state
- Aggregate at an SC level?
- Services: Status and deploy and mgmt
- Global admin...
- / - System status (dashboard...)
EnvironMint - random ideas
- Provision to ephemeral infra
- Docker/VM/...
- Use for tutorials/demos
- Also use as a configuration method
- Preconfigured with a DriftGuard agent
- Tom creates and tells Jed details
- Jed configures the sandbox to spec/standard
- Jed tells Tom the sandbox can be "harvested"
- Tom harvests the sandbox as new/updated service catalogue items
Sandbox
EnvironMint - random ideas
- Tweak/extend Mintspec (?) to act as a lighthearted alarming system?
Alarming
Install: Tom
- Provided with required artefact
- Feels like a single script
- Runs installer steps for EnvironMint...
- Asks for licence and confirms desired features
- A little sales-pitch-ish about features eg
- Main installer installs and configures all deps
- Option to get `customerX.environmint.io`
- Let's Encrypt cert
- Useful as an Apex record for internal?
- Simplifies internal IT reqs?
- Self bootstrapping Chef run
-
↓
Install: Tom
- Tell Tom some key details:
- Urls
- Possibly a demo access key? (for APIs)
- Suggests a tutorial...
- Tom starts doing the tutorial...
- Creates a Weblogic (and deploys a war?
- Scales it
- Applies a patch
- Rolls it out
- Changes some config
- Rolls it out
- Pushes it back into mainline?
As a Suite
- Console leverages DG functionality
- Harvesting in Sandbox
- DG -> Mintspec
- Console -> Mintspec
- Shared auth (seamless SSO, as well as LDAP etc)
-
Alarming-ish? -> Mintspec
- Maybe just frame as "system status"
- Environmint Dashboarding
- Pull in widgets/reports from everywhere, in one central location, not in individual apps
-
Mintpress reporting
- The stuff Vicki wants, and maybe more?
Environmint
By bruce_one
Environmint
- 57