# Climact On-boarding Meeting 13/09/22
## Tools
### Dev
- **Bitbucket** for version control
- 10000 Build minutes with Bitbucket subscription.
- Could be changed.
- A presentation could be made to change.
- They are anticipating a price.
- Gitlab could be possible
- Particularly just for the CI/CD
- **Jira**
- Will not have access
- tasks will be clear and specific
- **Docker Hub**
- Q: Manually pushed?
- A:
- Two tags for images
- One for with model
- One for without
- Web Tool not running in Docker
- **AWS**
- Route53?
- **Gandi** for domains
- Just the domain registrar?

### Communication
- **OneNote**
- We are encouraged to use it.
- They want better documentation
- **Teams**

## CI/CD Epic

The main task will be the automating the **Release pipeline**.

The pace of release is every week.

Releases are done locally first.

---

Q: Notifications come from the experts, and that signifies a need for a new release? How does that fit into the weekly release schedule?

A:

---

Q: I imagine there could be an issue in the manual process of

### To Research
- **DAG**
- Possibility for automation
- Ansible could be used for the deployment process

## Infrastructure

- Current Expenditure is around €1000/month
- Test server could be automatically created and destroyed in a CI/CD pipeline.
- Tailscale and/or AWS VPN solution
- Tailscale SSH could be _very useful_.
- Or automatically pulling Public keys from Github/Gitlab/Bitbucket

### To Research
- Check to see if bitbucket had a public key endpoint for users

## Glossary

**Sectors**:

A specific area of data analysis. For example, the energy sector.

**Nodes**:

**Model**:

This is the DAG in Knime

**Data**:

This is the information being provided to the model

**Pathways**:

aka scenario

Can be seen as configuration on the model

## Next Steps

- [ ] Formalize teams
- [ ] Send contact details

- Next meeting:
- 16th September

## Contact Details

**Vincent**: [[e-mail]](mailto:[e-mail] "mailto:[e-mail]")
- Off on Thursdays

**Thomas**: [[e-mail]](mailto:[e-mail] "mailto:[e-mail]")