Updated 08.02.17: Project Catch Up with @misterbisson (markdown)
Alex Jones
parent
c9f93c8c84
commit
036b1ff82a
@ -1,10 +1,216 @@
|
||||
**Present from Joyent:** @misterbisson
|
||||
|
||||
|
||||
**Present from Make Us Proud / YLD:** @antonasdeduchovas, @alex-windett, @juditgreskovits, @ajones5876, @ramitos, @AnthonyMann
|
||||
# **Project Catch Up**
|
||||
|
||||
## 1.) Questions from yesterday's meeting
|
||||
**Skype, 08.02.17**
|
||||
|
||||
## **Meeting aim**
|
||||
|
||||
* To discuss priorities for the next six months
|
||||
|
||||
**Joyent: **
|
||||
|
||||
* **Casey Bisson **
|
||||
|
||||
**MUP/YLD: **
|
||||
|
||||
**Anthony, Antonas, AJ, Alex, Judith, Sergio**
|
||||
|
||||
## **Agenda **
|
||||
|
||||
1. **Our list of priorities over the next six months:**
|
||||
|
||||
* Document outlining everything we have worked on so far: [https://drive.google.com/open?id=1OwdoSk3CT0IXQWDrcLtrf_ZtffhQ6OaCYIHETE3wkQU](https://drive.google.com/open?id=1OwdoSk3CT0IXQWDrcLtrf_ZtffhQ6OaCYIHETE3wkQU)
|
||||
|
||||
* The below table was created by thinking about what is the MVP (Alpha), what is the MLP (Beta) and then what are supplementary features we could create if we had time (Growth).
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>Alpha (High Priority)</td>
|
||||
<td>Beta (Medium Priority)</td>
|
||||
<td>Growth</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Highest Priority</td>
|
||||
<td>Sign up</td>
|
||||
<td>Deploying instances</td>
|
||||
<td>Container pilot catalogue</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>Deploying with Git</td>
|
||||
<td>Activity Feed</td>
|
||||
<td>Volumes/manta</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>Stopping/starting/ reprovisioning</td>
|
||||
<td>Deployment Queue</td>
|
||||
<td>Duplicating/ copying a project</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>Scaling</td>
|
||||
<td>Automatic Deployment</td>
|
||||
<td>Transferring</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>RBAC</td>
|
||||
<td>Adding instances/services</td>
|
||||
<td>Deploying by uploading manifest</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>Taxonomy/
|
||||
Navigation</td>
|
||||
<td>Rollback/updates/
|
||||
version control</td>
|
||||
<td>Deploying by writing manifest</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>Visualising Metrics</td>
|
||||
<td>Adding/editing metrics</td>
|
||||
<td>Security auditing</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>Billing Management</td>
|
||||
<td>Setting up alerts</td>
|
||||
<td>Environments</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>GitHub version syncing/
|
||||
visualisation</td>
|
||||
<td>Logs</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>Deleting</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Lowest Priority</td>
|
||||
<td>MOBILE</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
|
||||
## Other:
|
||||
* Growth: how can we bring in the wider Joyent ecosystem?
|
||||
|
||||
2. **Our priorities for the technical prototype:**
|
||||
|
||||
* The below table was created by thinking about the features that can only be tested in a technical prototype, for example ‘visualising metrics’ as this feature needs live data for a user to understand how this feature works correctly.
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>High Priority</td>
|
||||
<td>Medium Priority</td>
|
||||
<td>Low Priority</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Highest Priority</td>
|
||||
<td>Taxonomy/ Navigation</td>
|
||||
<td>Adding & Editing metrics</td>
|
||||
<td>Stop/start/
|
||||
reprovisioning</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>Visualising Metrics</td>
|
||||
<td>Setting up alerts</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>GitHub Deploy</td>
|
||||
<td>Logs</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td>
|
||||
<td>Scaling</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Lowest Priority</td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
<td></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
|
||||
3. **New wireframes**
|
||||
|
||||
* *Managing organisations - **[https://marvelapp.com/4jgd2h*e](https://marvelapp.com/4jgd2he)
|
||||
|
||||
* *Scaling, deployment queue and activity feed narrative - https://marvelapp.com/1d5f3dg*
|
||||
|
||||
4. **Technical Update**
|
||||
|
||||
* *Judith to place link here*
|
||||
|
||||
5. **Questions?**
|
||||
|
||||
* If not asked already, are we happy with a heavily reliance on GitHub?
|
||||
|
||||
* Do we just focus on implementing Docker style instances?
|
||||
|
||||
1. Infrastructure and hardware/VMS
|
||||
|
||||
2. Are we using the correct terminology here?
|
||||
|
||||
* Third party metrics solutions. Is Prometheus the preferred one?
|
||||
|
||||
* When rolling back a service, does this then create a new version of the project?
|
||||
|
||||
6. **What’s next? **
|
||||
|
||||
## **Meeting notes:**
|
||||
|
||||
* Casey will go through priorities and suggest some improvements
|
||||
|
||||
* Casey suggested that GitHub versioning shouldn’t necessarily be a priority, the source of truth stays inside Joyent: the product
|
||||
|
||||
* The users could use a CI tool, such as [https://jenkins.io/](https://jenkins.io/), to maintin synchronisity with GitHub/GitLab etc : this does need some clarification
|
||||
|
||||
* In the short term the asynchronousy between joyent manifest and github manifest is in back lock for the time being.
|
||||
|
||||
* [https://github.com/joyent/rfd/blob/master/rfd/0036/stories/jupiter-example-com-jenkins.md](https://github.com/joyent/rfd/blob/master/rfd/0036/stories/jupiter-example-com-jenkins.md)
|
||||
|
||||
* Joyent CLI tools to encompass GitHub integration instead.
|
||||
|
||||
* Versioning:
|
||||
|
||||
* This is v. important and has to be done very well.
|
||||
|
||||
* When creating an update, we use this update more as a pointer, than a role back
|
||||
|
||||
* Casey will provide some clarification here
|
||||
|
||||
* Links Casey shared to try and explain this: [https://github.com/misterbisson/rfd/blob/rfd36-kiener-feedback/rfd/0036/README.md#project](https://github.com/misterbisson/rfd/blob/rfd36-kiener-feedback/rfd/0036/README.md#project)
|
||||
|
||||
* [https://github.com/misterbisson/rfd/blob/rfd36-kiener-feedback/rfd/0036/projects/triton-projects-cli.md#triton-project-reprovisionrestart---serviceservice-name-or-uuid---versionversion-uuid---imageimagespectag---instancenameuuid---compute_nodeuuid---countcanarypositive-integer-rollingpositive-integer](https://github.com/misterbisson/rfd/blob/rfd36-kiener-feedback/rfd/0036/projects/triton-projects-cli.md#triton-project-reprovisionrestart---serviceservice-name-or-uuid---versionversion-uuid---imageimagespectag---instancenameuuid---compute_nodeuuid---countcanarypositive-integer-rollingpositive-integer)
|
||||
|
||||
* When you rollback you change the default / active manifest to a previous version but the latest version is not used or deleted.
|
||||
|
||||
* There maybe be something that you get current logs and metrics but previous or past history is something that is yet to come.
|
||||
|
||||
* Maybe bump these up to alpha
|
||||
|
||||
* Casey brought Richard onto the call who gave us a tour of Prometheus: [https://prometheus.io/](https://prometheus.io/)
|
||||
|
||||
* Recorded video of this tour is in Slack: [https://joyent-portal.slack.com/files/alexjones/F437DLVEK/zoom_0.mp4](https://joyent-portal.slack.com/files/alexjones/F437DLVEK/zoom_0.mp4)
|
||||
|
||||
* Need to support traditional and unmanaged instances. This include VMs
|
||||
|
||||
## Notes:
|
||||
Loading…
Reference in New Issue
Block a user