Skip to content

Commit

Permalink
TRITON-1694 create Triton Grafana image
Browse files Browse the repository at this point in the history
Reviewed by: Trent Mick <trentm@gmail.com>
Reviewed by: Alex Wilson <alex.wilson@joyent.com>
Reviewed by: Josh Wilsdon <josh@wilsdon.ca>
Approved by: Josh Wilsdon <josh@wilsdon.ca>
  • Loading branch information
Isaac Davis committed Jun 24, 2019
1 parent be9152b commit ddc3b17
Show file tree
Hide file tree
Showing 40 changed files with 4,543 additions and 12 deletions.
25 changes: 25 additions & 0 deletions .eslintrc
@@ -0,0 +1,25 @@
{
"plugins": [ "joyent" ],
"extends": [
"eslint:recommended",
"plugin:joyent/style",
"plugin:joyent/lint"
],
"parserOptions": {
"ecmaVersion": 6,
"sourceType": "script",
"ecmaFeatures": {
}
},
"env": {
"node": true
},
"rules": {
// Lint:
"strict": [ "error", "global" ],

// Style:
"func-style": [ "error", "declaration" ],
"multiline-comment-style": [ "error", "starred-block" ]
}
}
8 changes: 8 additions & 0 deletions .gitignore
@@ -0,0 +1,8 @@
/bits
/build
/cache
/grafana-pkg-*.tar.gz
/make_stamps
/node_modules
/npm-debug.log
/tmp
12 changes: 12 additions & 0 deletions .gitmodules
@@ -0,0 +1,12 @@
[submodule "deps/sdc-scripts"]
path = deps/sdc-scripts
url = https://github.com/joyent/sdc-scripts
[submodule "deps/nginx"]
path = deps/nginx
url = https://github.com/nginx/nginx
[submodule "deps/grafana"]
path = deps/grafana
url = https://github.com/joyent/grafana
[submodule "deps/eng"]
path = deps/eng
url = https://github.com/joyent/eng.git
5 changes: 5 additions & 0 deletions CHANGES.md
@@ -0,0 +1,5 @@
# triton-grafana changes

## 1.0.0

First version.
73 changes: 73 additions & 0 deletions CONTRIBUTING.md
@@ -0,0 +1,73 @@
<!--
This Source Code Form is subject to the terms of the Mozilla Public
License, v. 2.0. If a copy of the MPL was not distributed with this
file, You can obtain one at http://mozilla.org/MPL/2.0/.
-->

<!--
Copyright 2019 Joyent, Inc.
-->

# Triton Contribution Guidelines

Thanks for using Triton and for considering contributing to it!

tl;dr:
- Triton repos do *not* use GitHub pull requests (PRs)! You'll be asked to
re-submit PRs to Gerrit. See below.
- Triton repos use both GitHub issues and internal-to-Joyent Jira projects for
issue tracking.


## Code

The Triton project uses Gerrit at [cr.joyent.us](https://cr.joyent.us) for code
review of all changes. Any registered GitHub user can submit changes through
this system. If you want to contribute a change, please see the [Joyent Gerrit
user
guide](https://github.com/joyent/joyent-gerrit/blob/master/docs/user/README.md).
If you're making a substantial change, you probably want to contact developers
[on the mailing list or IRC](README.md#community) first. If you have any trouble
with the contribution process, please feel free to contact developers [on the
mailing list or IRC](README.md#community). Note that larger Triton project
changes are typically designed and discussed via ["Requests for Discussion
(RFDs)"](https://github.com/joyent/rfd).

Triton repositories use the [Joyent Engineering
Guidelines](https://github.com/joyent/eng/blob/master/docs/index.md). Notably:

* The #master branch should be first-customer-ship (FCS) quality at all times.
Don't push anything until it's tested.
* All repositories should be "make check" clean at all times.
* All repositories should have tests that run cleanly at all times.

"make check" checks both JavaScript style and lint. Style is checked with
[jsstyle](https://github.com/davepacheco/jsstyle). The specific style rules are
somewhat repo-specific. See the jsstyle configuration file or `JSSTYLE_FLAGS`
in Makefiles in each repo for exceptions to the default jsstyle rules.

Lint is checked with
[javascriptlint](https://github.com/davepacheco/javascriptlint). Repos sometimes
have repo-specific lint rules, but this is less common -- look for
"tools/jsl.node.conf" for per-repo exceptions to the default rules.


## Issues

There are two separate issue trackers that are relevant for Triton code:

- An internal-to-Joyent JIRA instance.

A JIRA ticket has an ID like `IMGAPI-536`, where "IMGAPI" is the JIRA project
name -- in this case used by the
[sdc-imgapi](https://github.com/joyent/sdc-imgapi) and related repos. A
read-only view of most JIRA tickets is made available at
<https://smartos.org/bugview/> (e.g.
<https://smartos.org/bugview/IMGAPI-536>).

- GitHub issues for the relevant repo, e.g.
<https://github.com/joyent/triton/issues>.

Before Triton was open sourced, Joyent engineering used a private JIRA instance.
While Joyent continues to use JIRA internally, we also use GitHub issues for
tracking -- primarily to allow interaction with those without access to JIRA.

0 comments on commit ddc3b17

Please sign in to comment.