Milestones
List view
Deliverable: Presentation slides For your demo, your application must be: Organized and documented in a code repository Provided with an installation procedure Functional. The DataScientest defense is conducted in groups as follows: 20 minutes presentation & demo 10 minutes of questions from the jury members You have the option to either make: a presentation + demo live presentation of the system As an additional indicative guidance, here is the list of assessed competencies for the French DevOps Administrator professional title: Functional project Quality of code and tools Creation of a prototype final product Manage multiple environments Automate server creation and configuration using scripts Automate the provisioning of an infrastructure Secure the infrastructure Put infrastructure into production in the cloud Prepare a test environment Prepare unit tests before production Manage databases and data storage Manage containers Automate the production of an application with a platform for orchestration Define and implement a monitoring solution (SRE) Define and implement service statistics Operate a monitoring solution
No due dateSubject: monitor and collect system analysis data in its entirety and in the various environments to detect malfunctions and allow for improvement. Set up a centralized monitoring system (as a service or self-managed) Define and implement monitoring policies relevant to the application and in relation to the requirements defined for the: logs, metrics, "health points" Define and configure dashboards that meet the needs of their target users (DEVs, OPs, SREs, business...) Define events and levels that characterize a malfunction or significant state of the architecture or/and the application Define and implement the alert channels and policies used by the defined triggers. Deliverables Centralized and integrated solution that watches over the entire system Accessible dashboards Alert system in operation Bonus points: Define and implement automatic actions in response to alarms. Tracing support Define and create relevant performance and operational reports for different stakeholders Deadline : Week 5
No due dateSubject Create and configure data storage resources (block, file, object, databases, caches) Define and implement policies: authentication authorization and access control logging Data import Install and configure a data backup and restore solution Deliverables Operational and application/user accessible data according to defined requirements Backup/restore scripts and/or procedures Bonus points Resilience and high availability Scalability (volumes and performance) Business continuity/recovery solution(s): Policy, life cycle management and data backup system Recovery system in production and on backup infrastructure (cold/warm/hot) of backups Deadline : Week 4
No due dateSubject: define and automate the provisioning and configuration of system infrastructure and services using IaC/CaC tools and techniques. IAM/AAA (accounts, organizations, users, roles) Network (VPCs, subnets, gateways, endpoints, routes, NACL,...) Storage (services, endpoints, backup, ...) Compute Nodes (instances, images, configuration...) Orchestration (clusters) Security Secrets management Access and operational rights Securing the traffic Deliverables Root account, organization, and users Operational and compliant cloud infrastructure Infrastructure provisioning and configuration manifests, scripts, and files maintained in a VCS. Bonus points Business continuity/recovery solution(s): Infrastructure backup and restore Backup infrastructure (cold/warm/hot) Auto-scaling Advanced IAM/AAA (multi-account infrastructure, roles, policies, identity service) Deadline: Week 3
No due dateSubject: define and implement automation of the integration and deployment chain for infrastructure and applications. Separate environments (VMs/namespaces/clusters/VPCs) for each phase of the defined development cycle Necessary and adequate tests to ensure the proper functioning, quality and security of the components and the overall system. Automation integration and deployment activities like: static and unit testing, build/compile, delivery, deployment, dynamic testing (behavior, load, UAT, ...) Deliverables Provisioning of isolated deployment environments corresponding to the defined development, delivery and deployment cycle Test, build, delivery and deployment procedures Unified and automated processes for integration and deployment across branches and environments Bonus points Limit the risks of degradation of operation and interruption of service due to continuous deployment/delivery by using appropriate techniques (canary, blue/green, etc.) Measure the effectiveness and success of DevOps practices by collecting appropriate indicators (Deployment Cycle Time, Deployment Frequency, Deployment Success Rate). Deadline: Week 2 Note: This is potentially the most important step/component as it is the core of your project and DevOps practices.
Overdue by 1 year(s)•Due by June 1, 2025Subject Define the context, the objectives, as well as the scope of the project The context must define the environment and framework in which the project is held: stakeholders, expectations, deadlines... The scope is intended to outline the project and its objectives, especially according to resources and time available. It can also be defined by phases or levels. Collect and organize requirements: Functional requirements: those of the different users, of the internal and external stakeholders (devs, ops, SRE, marketing, product, users/customers,...). The structure of this part can therefore correspond to their roles. Non-functional requirements: those for the system itself. Apart from those possibly arising directly from the objectives, they arise from the functional requirement, for example, to have a service always as efficient (marketing, users) and reliable (SRE, Ops) whatever the load. Identify the components of the system architecture, their role and their interrelationships Study and select the solutions for the components Define the target system’s architecture and specifications Project (method, breakdown, assignment, planning, ...) Source code (flow, review, validation,...) CI/CD (development cycle stages, jobs, environments) Data (location, replication/distribution, links, access, caching, ...) Storage (type - DBMS / Block / File / Object, IOPS, volume, Backup, ...) Network (location, segmentation, addressing, routing, filtering, ...) Compute (nodes, autoscaling, containers, orchestration,...) Security (AAA, code, traffic, instances, ...) Observability (metrics, logs, traces, alerts) Continuity & Recovery (redundancy, failover, backup, BCP/DRP) Deliverables Requirements: Context, objectives, scope and requirements that will guide the project and be used for decision making in all subsequent phases. Detailed plan/outline/tables (will be used for the writing of the submission). Specifications Detailed plan/outline/tables of specifications Components diagram Solutions stack High-level functional, architectural, implementation schematics and diagrams... Project & SCM Setup of the collaborative organization, users, project, milestones, first epics/stories/issues Repositories: strategy (mono/multi), structure (app, infra, modules, charts, etc.), and initialization Source code management flow (Git flow, GitLab Flow, etc.) and branches Bonus points Creation/initialization of accounts, organizations, projects... on the collaborative platform/SCM/CI/CD and at the cloud provider using IaC. Project and code repository(ies) backup Remarks To help you in structuring your thinking and your productions (texts, diagrams, etc.), try to always follow the business/architectural/process/implementation logic. Depending on the relevance of one or the other, you can follow a top-down/bottom-up/input-output/... approach Don’t spend time on writing, don’t waste time making sentences at this stage, you’ll have plenty of time for the submission! Make your requirements collection a guide and grid for design and specification. Deadline : 25th, August 2025
Overdue by 1 year(s)•Due by May 25, 2025•1/1 issues closed