Magic Partition Recovery V2.3 With Serial Keys

Magic Partition Recovery V2.3 With Serial Keys

Download File ::: https://urloso.com/2t2FhX

Your Surface comes with Windows recovery information that allows you to refresh your device or reset it to its factory condition. This recovery information is stored in a dedicated recovery partition on your Surface.

Use the replicated storage levels if you want fast fault recovery (e.g. if using Spark to serverequests from a web application). All the storage levels provide full fault tolerance byrecomputing lost data, but the replicated ones let you continue running tasks on the RDD withoutwaiting to recompute a lost partition.

Note: If you are willing to accept downtime, you can simply take all the brokers down, update the code and start all of them. They will start with the new protocol by default.Note: Bumping the protocol version and restarting can be done any time after the brokers were upgraded. It does not have to be immediately after.Potential breaking changes in 0.10.1.0 The log retention time is no longer based on last modified time of the log segments. Instead it will be based on the largest timestamp of the messages in a log segment. The log rolling time is no longer depending on log segment create time. Instead it is now based on the timestamp in the messages. More specifically. if the timestamp of the first message in the segment is T, the log will be rolled out when a new message has a timestamp greater than or equal to T + log.roll.ms The open file handlers of 0.10.0 will increase by ~33% because of the addition of time index files for each segment. The time index and offset index share the same index size configuration. Since each time index entry is 1.5x the size of offset index entry. User may need to increase log.index.size.max.bytes to avoid potential frequent log rolling. Due to the increased number of index files, on some brokers with large amount the log segments (e.g. >15K), the log loading process during the broker startup could be longer. Based on our experiment, setting the num.recovery.threads.per.data.dir to one may reduce the log loading time. Upgrading a 0.10.0 Kafka Streams Application Upgrading your Streams application from 0.10.0 to 0.10.1 does require a broker upgrade because a Kafka Streams 0.10.1 application can only connect to 0.10.1 brokers. There are couple of API changes, that are not backward compatible (cf. Streams API changes in 0.10.1 for more details). Thus, you need to update and recompile your code. Just swapping the Kafka Streams library jar file will not work and will break your application. Upgrading from 0.10.0.x to 0.10.1.2 requires two rolling bounces with config upgrade.from="0.10.0" set for first upgrade phase (cf. KIP-268). As an alternative, an offline upgrade is also possible. prepare your application instances for a rolling bounce and make sure that config upgrade.from is set to "0.10.0" for new version 0.10.1.2 bounce each instance of your application once prepare your newly deployed 0.10.1.2 application instances for a second round of rolling bounces; make sure to remove the value for config upgrade.from bounce each instance of your application once more to complete the upgrade Upgrading from 0.10.0.x to 0.10.1.0 or 0.10.1.1 requires an offline upgrade (rolling bounce upgrade is not supported) stop all old (0.10.0.x) application instances update your code and swap old code and jar file with new code and new jar file restart all new (0.10.1.0 or 0.10.1.1) application instances Notable changes in 0.10.1.0 The new Java consumer is no longer in beta and we recommend it for all new development. The old Scala consumers are still supported, but they will be deprecated in the next release and will be removed in a future major release. The --new-consumer/--new.consumer switch is no longer required to use tools like MirrorMaker and the Console Consumer with the new consumer; one simply needs to pass a Kafka broker to connect to instead of the ZooKeeper ensemble. In addition, usage of the Console Consumer with the old consumer has been deprecated and it will be removed in a future major release. Kafka clusters can now be uniquely identified by a cluster id. It will be automatically generated when a broker is upgraded to 0.10.1.0. The cluster id is available via the kafka.server:type=KafkaServer,name=ClusterId metric and it is part of the Metadata response. Serializers, client interceptors and metric reporters can receive the cluster id by implementing the ClusterResourceListener interface. The BrokerState "RunningAsController" (value 4) has been removed. Due to a bug, a broker would only be in this state briefly before transitioning out of it and hence the impact of the removal should be minimal. The recommended way to detect if a given broker is the controller is via the kafka.controller:type=KafkaController,name=ActiveControllerCount metric. The new Java Consumer now allows users to search offsets by timestamp on partitions. The new Java Consumer now supports heartbeating from a background thread. There is a new configuration max.poll.interval.ms which controls the maximum time between poll invocations before the consumer will proactively leave the group (5 minutes by default). The value of the configuration request.timeout.ms (default to 30 seconds) must always be smaller than max.poll.interval.ms(default to 5 minutes), since that is the maximum time that a JoinGroup request can block on the server while the consumer is rebalance. Finally, the default value of session.timeout.ms has been adjusted down to 10 seconds, and the default value of max.poll.records has been changed to 500. When using an Authorizer and a user doesn't have Describe authorization on a topic, the broker will no longer return TOPIC_AUTHORIZATION_FAILED errors to requests since this leaks topic names. Instead, the UNKNOWN_TOPIC_OR_PARTITION error code will be returned. This may cause unexpected timeouts or delays when using the producer and consumer since Kafka clients will typically retry automatically on unknown topic errors. You should consult the client logs if you suspect this could be happening. Fetch responses have a size limit by default (50 MB for consumers and 10 MB for replication). The existing per partition limits also apply (1 MB for consumers and replication). Note that neither of these limits is an absolute maximum as explained in the next point. Consumers and replicas can make progress if a message larger than the response/partition size limit is found. More concretely, if the first message in the first non-empty partition of the fetch is larger than either or both limits, the message will still be returned. Overloaded constructors were added to kafka.api.FetchRequest and kafka.javaapi.FetchRequest to allow the caller to specify the order of the partitions (since order is significant in v3). The previously existing constructors were deprecated and the partitions are shuffled before the request is sent to avoid starvation issues. New Protocol Versions ListOffsetRequest v1 supports accurate offset search based on timestamps. MetadataResponse v2 introduces a new field: "cluster_id". FetchRequest v3 supports limiting the response size (in addition to the existing per partition limit), it returns messages bigger than the limits if required to make progress and the order of partitions in the request is now significant. JoinGroup v1 introduces a new field: "rebalance_timeout". Upgrading from 0.8.x or 0.9.x to 0.10.0.00.10.0.0 has potential breaking changes (please review before upgrading) and possible performance impact following the upgrade. By following the recommended rolling upgrade plan below, you guarantee no downtime and no performance impact during and following the upgrade.Note: Because new protocols are introduced, it is important to upgrade your Kafka clusters before upgrading your clients.

The configuration controls how long the KafkaProducer's send(), partitionsFor(), initTransactions(), sendOffsetsToTransaction(), commitTransaction() and abortTransaction() methods will block. For send() this timeout bounds the total time waiting for both metadata fetch and buffer allocation (blocking in the user-supplied serializers or partitioner is not counted against this timeout). For partitionsFor() this timeout bounds the time spent waiting for metadata if it is unavailable. The transaction-related methods always block, but may timeout if the transaction coordinator could not be discovered or did not respond within the timeout.

Converter class used to convert between Kafka Connect format and the serialized form that is written to Kafka. This controls the format of the keys in messages written to or read from Kafka, and since this is independent of connectors it allows any connector to work with any serialization format. Examples of common formats include JSON and Avro.

Topics are added and modified using the topic tool: > bin/kafka-topics.sh --bootstrap-server broker_host:port --create --topic my_topic_name \ --partitions 20 --replication-factor 3 --config x=y The replication factor controls how many servers will replicate each message that is written. If you have a replication factor of 3 then up to 2 servers can fail before you will lose access to your data. We recommend you use a replication factor of 2 or 3 so that you can transparently bounce machines without interrupting data consumption. The partition count controls how many logs the topic will be sharded into. There are several impacts of the partition count. First each partition must fit entirely on a single server. So if you have 20 partitions the full data set (and read and write load) will be handled by no more than 20 servers (not counting replicas). Finally the partition count impacts the maximum parallelism of your consumers. This is discussed in greater detail in the concepts section. Each sharded partition log is placed into its own folder under the Kafka log directory. The name of such folders consists of the topic name, appended by a dash (-) and the partition id. Since a typical folder name can not be over 255 characters long, there will be a limitation on the length of topic names. We assume the number of partitions will not ever be above 100,000. Therefore, topic names cannot be longer than 249 characters. This leaves just enough room in the folder name for a dash and a potentially 5 digit long partition id. The configurations added on the command line override the default settings the server has for things like the length of time data should be retained. The complete set of per-topic configurations is documented here. Modifying topics You can change the configuration or partitioning of a topic using the same topic tool. To add partitions you can do > bin/kafka-topics.sh --bootstrap-server broker_host:port --alter --topic my_topic_name \ --partitions 40 Be aware that one use case for partitions is to semantically partition data, and adding partitions doesn't change the partitioning of existing data so this may disturb consumers if they rely on that partition. That is if data is partitioned by hash(key) % number_of_partitions then this partitioning will potentially be shuffled by adding partitions but Kafka will not attempt to automatically redistribute data in any way. To add configs: > bin/kafka-configs.sh --bootstrap-server broker_host:port --entity-type topics --entity-name my_topic_name --alter --add-config x=y To remove a config: > bin/kafka-configs.sh --bootstrap-server broker_host:port --entity-type topics --entity-name my_topic_name --alter --delete-config x And finally deleting a topic: > bin/kafka-topics.sh --bootstrap-server broker_host:port --delete --topic my_topic_name Kafka does not currently support reducing the number of partitions for a topic. Instructions for changing the replication factor of a topic can be found here. Graceful shutdown The Kafka cluster will automatically detect any broker shutdown or failure and elect new leaders for the partitions on that machine. This will occur whether a server fails or it is brought down intentionally for maintenance or configuration changes. For the latter cases Kafka supports a more graceful mechanism for stopping a server than just killing it. When a server is stopped gracefully it has two optimizations it will take advantage of: It will sync all its logs to disk to avoid needing to do any log recovery when it restarts (i.e. validating the checksum for all messages in the tail of the log). Log recovery takes time so this speeds up intentional restarts. It will migrate any partitions the server is the leader for to other replicas prior to shutting down. This will make the leadership transfer faster and minimize the time each partition is unavailable to a few milliseconds. Syncing the logs will happen automatically whenever the server is stopped other than by a hard kill, but the controlled leadership migration requires using a special setting: controlled.shutdown.enable=true Note that controlled shutdown will only succeed if all the partitions hosted on the broker have replicas (i.e. the replication factor is greater than 1 and at least one of these replicas is alive). This is generally what you want since shutting down the last replica would make that topic partition unavailable. Balancing leadership Whenever a broker stops or crashes, leadership for that broker's partitions transfers to other replicas. When the broker is restarted it will only be a follower for all its partitions, meaning it will not be used for client reads and writes. To avoid this imbalance, Kafka has a notion of preferred replicas. If the list of replicas for a partition is 1,5,9 then node 1 is preferred as the leader to either node 5 or 9 because it is earlier in the replica list. By default the Kafka cluster will try to restore leadership to the preferred replicas. This behaviour is configured with: auto.leader.rebalance.enable=true You can also set this to false, but you will then need to manually restore leadership to the restored replicas by running the command: > bin/kafka-leader-election.sh --bootstrap-server broker_host:port --election-type preferred --all-topic-partitions Balancing Replicas Across Racks The rack awareness feature spreads replicas of the same partition across different racks. This extends the guarantees Kafka provides for broker-failure to cover rack-failure, limiting the risk of data loss should all the brokers on a rack fail at once. The feature can also be applied to other broker groupings such as availability zones in EC2. 2b1af7f3a8

https://sway.office.com/jbTGjxcyWVMLJjSt

https://sway.office.com/nuVfR7NsgB1xBdsM

https://sway.office.com/C8reN09lw9xFuX2W

https://sway.office.com/PpCNM6Fi0mD4NKLH

https://sway.office.com/i1D0B80Lx5O3orbS

https://sway.office.com/pAYhoiDR81aAnUdE

https://sway.office.com/Gg5F351vDhLgPfpd

https://sway.office.com/iAlhGyWYPlLAzBoz

https://sway.office.com/Eu9qkzR5r1IjgBbN

https://sway.office.com/bC3eYVUcomD1Y0Wp

https://sway.office.com/SGMYpvaTkKnsHraC

https://sway.office.com/4egT7nPsWIT1juka

https://sway.office.com/9f9OxiEGMqINtpzF

https://sway.office.com/JI96PEo8camVVSmJ

https://sway.office.com/5VjWajKJXmXqzF6H

https://sway.office.com/YrYDUnAd2rzWzFuB

https://sway.office.com/QlZmgIGPhXoKHkgQ

https://sway.office.com/QHculi1r6yCSxjOe

https://sway.office.com/lAvmxDlCqZeoGDOH

https://sway.office.com/3QnAbCjIFgHwBtJq

https://sway.office.com/ezOVpm7jok1GVTlR

https://sway.office.com/nb1ClnvWuFCkJ8Rw

https://sway.office.com/K1KvbBk2GvrhNoIq

https://sway.office.com/IwLDPsRzhtdGLaka

https://sway.office.com/xkd5fEBd5ybGhMTX

https://sway.office.com/iqrafD4GJcpVh4ZF

https://sway.office.com/v5HKkiIMs0RtCxwH

https://sway.office.com/JMaejZdOh4XkR3Tn

https://sway.office.com/zRpoPv4s95lDtcwl

https://sway.office.com/0zrt8MhLJDlF23DD

https://sway.office.com/liKDBrvKAIlVDKLG

https://sway.office.com/TOxXnXehYqDzrFa3

https://sway.office.com/8ehYTUXypocLTyQ0

https://sway.office.com/dPrMGSJo1AEQDrA0

https://sway.office.com/Z0f9i2txqmB5qNID

https://sway.office.com/dFZrAF1J0kkHk2uB

https://sway.office.com/100HDootUSAUlOn6

https://sway.office.com/1fYw8k4qh1seCzcq

https://sway.office.com/g3t2wSldGlHycKJw

https://sway.office.com/0CwWXmJgMLjahhMZ

https://sway.office.com/PQjb7sGkGwyGYSXH

https://sway.office.com/021qj6bl1PVW4QxH

https://sway.office.com/LpEQuEij1fuwZQ5d

https://sway.office.com/0Pvq7vGjuReAs8fn

https://sway.office.com/JzMWRIgC6dIJDUDz

https://sway.office.com/qKLwh9ukj84Axx86

https://sway.office.com/DPHXJlEUAaqrbtWh

https://sway.office.com/3I91iR5CK9lADVdn

https://sway.office.com/lkU1qOADFGkF4fHj

https://sway.office.com/zD1QzAgUiOA1ktNs

https://sway.office.com/OiDHBlM3yQKkclWB

https://sway.office.com/nM0CrSoQltmkAzuh

https://sway.office.com/qjgkTzV1OPUD3y7N

https://sway.office.com/GW6vKmig9Ms35hbi

https://sway.office.com/wBF2yWzwLxDhoHIL

https://sway.office.com/i5V0SfwPCyliWt1G

https://sway.office.com/yuWtolv9V8UtdCb3

https://sway.office.com/WWGz71nbcUe6ZCF8

https://sway.office.com/TeFzB0U1HmB3UnHV

https://sway.office.com/0qq0nKONfZExoPTG

https://sway.office.com/8cIthBUMSsONekIL

https://sway.office.com/tkw0t4RYkha4sPlI

https://sway.office.com/kUQm3ZBTLqpbuOq8

https://sway.office.com/SkuwZb73Czp9MCR0

https://sway.office.com/napGLFzdsPl8j3oD

https://sway.office.com/sAFG1Lg4AOVUXwBr

https://sway.office.com/iwneVrxqGnj0F3U7

https://sway.office.com/9zuWms4oTiruiXJN

https://sway.office.com/FeO7poG0qtxJi2RV

https://sway.office.com/oNbuAU8WNTd0WEml

https://sway.office.com/XgOrDEXKnrAcA04n

https://sway.office.com/soA0Y1cqPQnRkgwo

https://sway.office.com/OesGbLp4TVh9zmeu

https://sway.office.com/Hg8lVTFHnf32OlQH

https://sway.office.com/IO9XlQxn4QGYEBUz

https://sway.office.com/zjQxRaULqLoSFHMJ

https://sway.office.com/zpF0jYpU47bq0VHX

https://sway.office.com/mNcBjGsCDGD7Fee5

https://sway.office.com/MVmHwfQxYSWkccmX

https://sway.office.com/AiC09hkrq5icI90t

https://sway.office.com/5PM4nExTTZwBDelB

https://sway.office.com/GoWN4gWpjoHovt5q

https://sway.office.com/jX7g7FjxlDiqrfOa

https://sway.office.com/y5jalRnt6sHQsIF6

https://sway.office.com/AatqKWpoAAHCiD31

https://sway.office.com/c8J6teUN127A0ER5

https://sway.office.com/JUR0zoZgqfUor8ED

https://sway.office.com/bRpMPVOAbQcJGYFp

https://sway.office.com/csDE2fgfNp4T87BB

https://sway.office.com/3AlfvgbemR2iNBvw

https://sway.office.com/0c8z3iWyRvhPG95U

https://sway.office.com/KBJHFYM3Pa1QxHVa

https://sway.office.com/1Y6fO6rxhffdBKar

https://sway.office.com/fjjhcRCASq66QXEW

https://sway.office.com/iIEKIz2y1PcCI11D

https://sway.office.com/jBYFfMuWllCfmHbW

https://sway.office.com/DwvVHKP2MDBsMeAe

https://sway.office.com/vDuLppstwmyDKWCh

https://sway.office.com/RRkwFHWiKQ0fqfvU

https://sway.office.com/I8OBsfqIHbFGuuFU

https://sway.office.com/5ZgZwvAjoZK5Wb4E

https://sway.office.com/5PxrHFQ6qRN9XPio

https://sway.office.com/j8ceSxVXJwwEHokt

https://sway.office.com/0Qa4NEbpUqw4up8x

https://sway.office.com/DuOwcETM2VH6I3SK

https://sway.office.com/m4Clzy9IFErIjtV7

https://sway.office.com/8mCAIiBxhOnKUwZg

https://sway.office.com/dyi0dAY58Zf30sFF

https://sway.office.com/6xyuroUCariwOho3

https://sway.office.com/5x6BqohjbY0AMPgP

https://sway.office.com/OGXn0FBFkFB43qSX

https://sway.office.com/WQE1IMAKylQkVhqy

https://sway.office.com/SB1zR8g15rRDXnub

https://sway.office.com/BiI3XPPANq5KjklJ

https://sway.office.com/gnkDtjxH4TbCGjkS

https://sway.office.com/llA5Dz8AlCMF0zPk

https://sway.office.com/HJlyhxhcOhosAXsB

https://sway.office.com/70hjKRVh4T94F7aY

https://sway.office.com/jC4JBGzpofr7syA1

https://sway.office.com/9h4YCPs8MJfSKNzN

https://sway.office.com/5pimfghJtXFcee1E

https://sway.office.com/tQXW2HFRjBDsc2Al

https://sway.office.com/HFg4TExJTjI8pWTC

https://sway.office.com/OpMpbtrCfPddn5iF

https://sway.office.com/kbBTsrsbydTZsiGg

https://sway.office.com/IKpQQraNLLDjVsBC

https://sway.office.com/0kSKY5FneVq78HJP

https://sway.office.com/mGyfuHoYdUpWxqWv

https://sway.office.com/gVkAytOJIxvaG2L5

https://sway.office.com/7RGtvY1P84txx015

https://sway.office.com/pjkEafWLgOMED5r3

https://sway.office.com/QnE41wrUzFie9DT5

https://sway.office.com/QIcomUr9avVOuABh

https://sway.office.com/fuphmKlsrCuQlMch

https://sway.office.com/IqHjmUG1Qd5UaqGp

https://sway.office.com/5GF8KQFBjkAJO5Oy

https://sway.office.com/GVZ55aGvNVKZJ8Zn

https://sway.office.com/Vk6yj1WGFSMCO2VW

https://sway.office.com/ufiEMM5g5BF8eRUl

https://sway.office.com/KWGHwT44dXtDK9gt

https://sway.office.com/EjQKxaNBPmxpDlDu

https://sway.office.com/dl3sOiDLnMcYJe8r

https://sway.office.com/4CcBpAbAWnABGXn8

https://sway.office.com/JfeTmTfTBdJIqUAB

https://sway.office.com/WLVCi8wD2qLqi758

https://sway.office.com/FzQHTMai27huqssD

https://sway.office.com/h7LkoPrU6S5sLT7P

https://sway.office.com/ezBuqFD00NaGsSU7

https://sway.office.com/iq13WAcqnqiRomqw

https://sway.office.com/Q5WUzeQkQ3Hnp5C9

https://sway.office.com/uTlP2RSNDbWNxpgi

https://sway.office.com/r2fnyi8gHEjqSHGK

https://sway.office.com/1HaOVhH6RZD7wYBG

https://sway.office.com/4MzrPAT2DeZamdzA

https://sway.office.com/cb6RjZk0w60KPfuw

https://sway.office.com/LFOXP5afOKPTrTZA

https://sway.office.com/Hk6gVDB3pd3iLjMi

https://sway.office.com/IbhBw2lS25DxhtSO

https://sway.office.com/fht9iS0Ia6v96UPy

https://sway.office.com/BjBtyW0uomXHzAid

https://sway.office.com/RoaufLMQ5bPpGPCL

https://sway.office.com/LuoJFFlDkZhNyM2V

https://sway.office.com/HFq5LGJkVJSeBfbn

https://sway.office.com/hUPmPQcPRlCZbSVL

https://sway.office.com/XAUXCBRXwvhElg06

https://sway.office.com/FOABfMyx5vRIXrrl

https://sway.office.com/nhyFj2ONJMPYRSAY

https://sway.office.com/NTbFhNc7EO545FxO

https://sway.office.com/pt4ACPW6ltbqI6w6

https://sway.office.com/AJ6mf1azBzxScYkA

https://sway.office.com/4KhiSyEJDVOxnI0y

https://sway.office.com/J9Vse27X1yydFzOr

https://sway.office.com/tmZ4bEYRAEtKUKCm

https://sway.office.com/IcoHxRx8EMkrEj9v

https://sway.office.com/UkGGpmFKAMFuSGti

https://sway.office.com/xsjagH0F31MEB7Cj

https://sway.office.com/J6cZbeRfiuwSwD4q

https://sway.office.com/xlNppTGKItnJeyPN

https://sway.office.com/YGAh61B01eLC9TDD

https://sway.office.com/nEHYATGLf12mtOGT

https://sway.office.com/nKqRyLB08PFeqp9b

https://sway.office.com/QweMSu0TG35Yfje1

https://sway.office.com/li2LbNQhRUFvULpZ

https://sway.office.com/0PyV3et8ndxttiHz

https://sway.office.com/6ZkyJmsIcjoPiGHE

https://sway.office.com/HdcFS88IlFUy2Aw6

https://sway.office.com/pssGhFflsEahmUGX

https://sway.office.com/sVIVEHH2CHT3WlVL

https://sway.office.com/vWBSD7Raup3czUq9

https://sway.office.com/4ztLFHcmV7ZBivTC

https://sway.office.com/QLR7xiQeePTFWzXT

https://sway.office.com/hzetWcX03RooMCXY

https://sway.office.com/UsScAheAruyFJkm4

https://sway.office.com/vkR0wOfDlL3eJSvr

https://sway.office.com/drAoAA1ppXB644ZB

https://sway.office.com/RIf3O8iSdUjmtICd

https://sway.office.com/Qsf924JnzWo0ZVr1

https://sway.office.com/3I5F5N2smf9cfpC8

https://sway.office.com/HsY5EfldONJRwe6J

https://sway.office.com/DInbO3jYyNlmTwMU

https://sway.office.com/yMqEqFDUllIybIP5

https://sway.office.com/26HsbDwGmIv8rgYe

https://sway.office.com/ZwxUcBoB6JaNns7k

https://sway.office.com/gtHhZ41e2yvN8EQU

https://sway.office.com/PACjrBPjq5tNPQ3N

https://sway.office.com/K7b4VqsRhV3QCFVZ

https://sway.office.com/fLzL263KVGbZ2jL9

https://sway.office.com/SvUnVuQ3aIYCAqva

https://sway.office.com/aiI1NGhbW3RxXwrz

https://sway.office.com/Oizq4CdsGbawCnHb

https://sway.office.com/9pSCg7OokgxYD3ET

https://sway.office.com/TelIZn9zxInzwe7G

https://sway.office.com/apRoMmGLjsu4j8ak

https://sway.office.com/FqXtWZCTjdy4qQqg

https://sway.office.com/nAnBBZ8QM4fMCgtn

https://sway.office.com/6j6Pg5KDBq1RAiYP

https://sway.office.com/55l7I8fXUIkFx4Yz

https://sway.office.com/y36LtTejh5OnwSVz

https://sway.office.com/L6WJgY15AZpLrvIq

https://sway.office.com/p9yu1zf1v9VZiHsn

https://sway.office.com/7CvKm8Dfw7YTZBMq

https://sway.office.com/ngo2JDW7XJSJfyXh

https://sway.office.com/XLEMfzL5dzN5hPS0

https://sway.office.com/IVEEfOGBpmHz5aLd